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.
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.
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.
This tool helps AI assistants and developer tools securely access your organization's internal information. It takes natural language questions from users of AI tools and provides answers drawn from your company's documents, wikis, and employee data, all while respecting existing access permissions. It's for IT administrators or operations teams looking to connect their organization's knowledge base with AI assistants.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work