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 available at: 
<app-url>/mcp
  • Transport — Streamable HTTP
  • Authentication — OAuth 2.0 via the app’s built-in provider

​
Excluding procedures

To exclude a procedure from MCP exposure: 
internalSync: scopedProcedure([])
  .meta({ description: 'Internal data sync', mcp: false })
  .mutation(...)
The procedure remains available via the HTTP API and to the built-in AI agent.