plugged.in MCP Hub — Proxy · Knowledge · Memory · Tools

The plugged.in MCP Proxy Server operates as a central hub that aggregates multiple Model Context Protocol (MCP) servers into a single, unified interface. It orchestrates knowledge, memory, and tools across connected MCPs, enabling clients to query documents, manage memory, and invoke tools from various servers through one connection. With support for STDIO, Server-Sent Events (SSE), and Streamable HTTP transports, it enables seamless integration with popular MCP clients like Claude Desktop, Cline, and Cursor while providing policy, telemetry, and registry features for scalable deployments.

This proxy fetches tool, prompt, and resource configurations from the plugged.in App APIs and exposes a unified catalog of capabilities. It supports static built-in tools, memory clipboard operations, and dynamic tools discovered from connected MCP servers, including tool discovery, RAG-based search, document management, and notifications. The hub also offers configuration options for HTTP transport, authentication, and session management, making it possible to run as a stateless HTTP service or a stateful STDIO proxy, with optional API-key protection for HTTP endpoints.

The plugged.in MCP Hub provides a single entry point to manage and query multiple MCP servers. It centralizes tool discovery, document management, and memory operations, making it easier to build AI workflows that span many data sources.

Example usage:

npx -y @pluggedin/pluggedin-mcp-proxy@latest --pluggedin-api-key YOUR_API_KEY

{
  "mcpServers": {
    "pluggedin": {
      "command": "npx",
      "args": ["-y", "@pluggedin/pluggedin-mcp-proxy@latest"],
      "env": {
        "PLUGGEDIN_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

npx -y @pluggedin/pluggedin-mcp-proxy@latest --pluggedin-api-key YOUR_API_KEY

npx -y @pluggedin/pluggedin-mcp-proxy@latest --transport streamable-http --pluggedin-api-key YOUR_API_KEY