Skip to main content
Every app exposes an MCP (Model Context Protocol) server that external AI tools can connect to.
  • All tRPC procedures with .meta({ description }) are registered as MCP tools
  • Tool calls go through the full tRPC middleware chain (JWT auth, RBAC, RLS)
  • Uses Streamable HTTP transport with session-based mode
  • Already wired up in the framework — no app code needed
AI tools like Claude Desktop, Cursor, and other MCP-compatible clients can connect to the app’s MCP server to call procedures as tools. Each tool call is authenticated, scope-checked, and logged.

​
Connecting

The MCP server is served on the app’s API origin, at the /mcp path — not the app’s page address:
The API origin is generated from where the app is deployed, so you can’t assemble it by hand: it may sit on a numbered shard or a custom (vanity) domain. The exact URL is shown at the top of the app’s API & MCP Access page (user menu → API & MCP Access) — copy it from there. Pointing a client at the app’s page host instead is the most common connection mistake.
  • Transport — Streamable HTTP
  • Authentication — OAuth 2.0 via the app’s built-in provider
For a step-by-step walkthrough of connecting Claude Desktop or another client, see Connect to a Deployed App Over MCP.

​
Excluding procedures

To exclude a procedure from MCP exposure:
The procedure remains available via the HTTP API and to the built-in AI agent.