Model Context Protocol
Veltor exposes the same domain actions through a vendor-neutral remote MCP server using standard Streamable HTTP.
What MCP adds
MCP lets an authorized coding agent, IDE, cowork tool, or automation client discover Veltor tools and call them with structured input. MCP does not give a model extra authority; credentials, scopes, environment checks, role checks, idempotency, and audit rules still apply.
Remote endpoints
Connect Test clients to https://veltor.dev/mcp/test and Live clients to https://veltor.dev/mcp/live. A standards-compliant client needs only the endpoint, OAuth discovery with PKCE or an API-key bearer header, and standard MCP messages.
Transport independence
The server does not require OpenAI-specific or Anthropic-specific tool formats, sampling, elicitation, model APIs, or proprietary approval callbacks. The optional @veltor/mcp bridge supports clients limited to local stdio.