Remote-MCP and remote-mcp-adapter

These are complementary tools—the type-safe remote communication framework (A) provides the underlying protocol layer that the config-driven proxy (B) builds upon to add session management, file handling, and state controls for upstream servers.

Remote-MCP

Emerging

remote-mcp-adapter

Experimental

Maintenance 0/25

Adoption 10/25

Maturity 9/25

Community 17/25

Maintenance 13/25

Adoption 2/25

Maturity 9/25

Community 0/25

Stars: 206

Forks: 28

Downloads: —

Commits (30d): 0

Language: TypeScript

License: MIT

Stars: 2

Forks: —

Downloads: —

Commits (30d): 0

Language: Python

License: MIT

Stale 6m No Package No Dependents

No Package No Dependents

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-adapter

aakashH242/remote-mcp-adapter

Config-driven MCP proxy that adds session-safe file uploads, artifact handling, and robust state and health controls for upstream MCP servers. Also provides code-mode for servers that don't yet support it.

Related comparisons

Remote-MCP and remote-mcp-server

Scores updated daily from GitHub, PyPI, and npm data. How scores work