tRPC <-> MCP allows you to serve tRPC routes as a Model Context Protocol (MCP) server, enabling seamless integration between tRPC and MCP. It supports TypeScript and enables custom metadata in routes.
tRPC <-> MCP allows you to serve tRPC routes as a Model Context Protocol (MCP) server, enabling seamless integration between tRPC and MCP. It supports TypeScript and enables custom metadata in routes.
Add this configuration to your claude_desktop_config.json:
{
"mcpServers": {
"trpc-mcp": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-trpc-mcp"
]
}
}
}Restart Claude Desktop, then ask:
"What tools do you have available from tRPC <-> MCP?"
No configuration required. This server works out of the box.
"What resources are available in tRPC <-> MCP?"
Claude will query available resources and return a list of what you can access.
"Show me details about [specific item] in tRPC <-> MCP"
Claude will fetch and display detailed information about the requested item.
"Create a new [item] in tRPC <-> MCP with [details]"
Claude will use the appropriate tool to create the resource and confirm success.
See what tools in your stack can connect to AI.
We build custom MCP integrations for B2B companies. From simple connections to complex multi-tool setups.