trpc-to-mcp
Enables engineering teams to expose existing tRPC endpoints as Claude MCP tools, reducing integration overhead and reusing validated business logic without r…
Turn tRPC procedures into MCP tools
- Convert existing tRPC API endpoints into callable MCP tools for Claude integration
- Expose backend tRPC procedures as Claude-compatible tools without rewriting code
- Automate bridging between your tRPC application and Claude's model context protocol
Enables engineering teams to expose existing tRPC endpoints as Claude MCP tools, reducing integration overhead and reusing validated business logic without rebuilding interfaces or authentication layers.
Backend teams maintaining tRPC APIs who want to expose procedures to Claude agents for automation and tooling.
https://www.npmjs.com/package/trpc-to-mcp
By GitHub Actions
How to Get It
npx -y trpc-to-mcp
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
Once it’s connected, paste this into Claude:
Help me convert existing tRPC API endpoints into callable MCP tools for Claude integration
Trust Signals Auto-scanned
Data & Access
Community Pulse Quiet
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 36 GitHub stars; contributors unknown; last commit 1d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 36 GitHub stars; contributors unknown; last commit 1d ago; license MIT.