Remote-MCP and remote-mcp-server
These are complementary tools: one provides the type-safe client/communication layer for remote MCP connections, while the other provides the server-side infrastructure for securely exposing enterprise context over remote MCP protocols.
About Remote-MCP
ssut/Remote-MCP
A type-safe solution to remote MCP communication, enabling effortless integration for centralized management of Model Context.
Implements a client-server architecture using tRPC over HTTP to decouple local MCP clients from remote resources, enabling centralized tool and resource management across distributed backends. The library provides type-safe bidirectional communication through separate `@remote-mcp/client` and `@remote-mcp/server` packages, with examples for Node.js and Cloudflare Workers deployments, and supports authentication via custom HTTP headers.
About remote-mcp-server
gleanwork/remote-mcp-server
Remote MCP Server that securely connects Enterprise context with your LLM, IDE, or agent platform of choice.
Implements the Model Context Protocol to expose enterprise knowledge through permission-aware search and retrieval, people discovery, and expertise identification. Uses OAuth 2.0 authentication with streamable HTTP transport for real-time communication with MCP-compatible clients. Works across IDE platforms (Claude Desktop, Cursor) and agent systems while enforcing organization's existing access controls.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work