Skip to content
Everruns Everruns

Model Context Protocol (MCP)

Everruns speaks the Model Context Protocol on both sides: it exposes its own agents and tools as an MCP server, and it consumes remote MCP servers as agent capabilities.

Everruns as an MCP server

Section titled “Everruns as an MCP server”

Every Everruns deployment exposes an MCP endpoint at /mcp so external clients — Claude Desktop, Cursor, VS Code, or another agent — can discover and call your agents and tools over JSON-RPC.

  • Transport — JSON-RPC 2.0 over Streamable HTTP (POST /mcp). Protocol versions 2025-06-18 and 2025-03-26 are supported.
  • Methods — initialize, ping, tools/list, tools/call, resources/list, resources/read.
  • Auth — the same org resolution as the REST API (API keys, JWT/cookie sessions), plus OAuth 2.1 with mandatory PKCE for dynamic client registration. Discovery metadata is served at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/mcp.
  • Entity cards — under protocol 2025-06-18, tools like agent_get_card return a sandboxed text/html MCP App resource at the ui:// scheme alongside a text summary, so MCP-Apps-aware hosts render rich cards while others fall back to text.

Routing is intentionally split: REST under /api/*, MCP OAuth under /oauth/*, and MCP JSON-RPC at /mcp.

Everruns as an MCP client

Section titled “Everruns as an MCP client”

Register a remote MCP server and its tools appear as a virtual capability — auto-discovered, namespaced, and executed alongside built-in capabilities. No code changes are needed to give an agent new tools.

  • Org-managed servers — organization-scoped McpServer records connect over remote HTTP (Streamable HTTP). stdio is rejected by the hosted control plane and is only available to single-tenant runtime/CLI hosts.
  • Scoped mcpServers — harnesses, agents, and sessions can embed remote MCP config directly (the remote-server subset of .mcp.json) for session-local or agent-local wiring without creating an org-global record.
  • Tool naming — discovered tools are namespaced per server so they never collide with built-in capabilities.

Use Everruns from your AI tools

Section titled “Use Everruns from your AI tools”

To connect Claude Code, Codex, or Cursor to a deployment via the everruns-dev plugin, see Use in AI tools.

Section titled “Related”
  • Capabilities — how virtual capabilities fit the capability system
  • Apps — publishing agents to channels