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 16/25

Community 17/25

Maintenance 10/25

Adoption 2/25

Maturity 11/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.

This helps developers who manage AI model contexts across different systems. It provides a way to centralize access to various model resources like databases and APIs, allowing local AI applications to connect to a single remote Model Context Protocol (MCP) server instead of multiple local ones. The end result is a more streamlined and manageable setup for integrating AI models with external tools and data.

AI-integration Model-context-management Developer-tools API-integration Distributed-systems

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 Remote-MCP and remote-mcp-server-registry

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