ssut/Remote-MCP
View on GitHub ↗A type-safe solution to remote MCP communication, enabling effortless integration for centralized management of Model Context.
209 ★25 forksTypeScriptUpdated 1y ago
What you need to know
A type-safe, bidirectional and simple solution for remote MCP communication — a local @remote-mcp/client bridges to a remote @remote-mcp/server over tRPC(HTTP) so local MCP clients can reach and centrally manage remote model contexts.
Install
Use the published client in your MCP client settings: npx -y @remote-mcp/client with REMOTE_MCP_URL and HTTP_HEADER_Authorization Server side: npm install @remote-mcp/server and stand up a tRPC HTTP server (MCPRouter)
Usage
- •Add remote-mcp to your MCP client config pointing at the remote URL
- •Build a remote server with MCPRouter and createTRPCRouter, then listen on a port
Key features
- ✓Type-safe client/server communication using tRPC over HTTP
- ✓Local client package exposing a local MCP server that proxies remote tools/prompts
- ✓Examples for Cloudflare Workers and standalone Node.js
Best for
Developers who need remote MCP access today, before official remote-MCP support matures.
Caveats
- ⚠Experimental and under active development — expect breaking changes
- ⚠Bidirectional communication, event subscriptions and auth middleware still on the roadmap
- ⚠Not part of the official MCP specification — a complementary extension
Platforms: Server · Cloudflare Workers · LocalClients: Claude · MCP clients
Reviewed 2026-08-11
Topics
- Stars
- 209★
- Forks
- 25
- Language
- TypeScript
- License
- MIT
- Created
- 2024-12-30
- Last push
- 2025-03-27