Hub

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.

MCP Bundles Hub MCP Server provides direct, unified access to tools from all your enabled MCP bundles through a single authenticated endpoint. It enables executing tools, discovering what tools are available across bundles, searching by name, provider, or capability, and checking readiness and details for each tool. This hub server consolidates bundle tools into one MCP interface, streamlining AI-assisted workflows by securely managing credentials and ensuring bundle-aware execution. Built with OAuth and API key authentication, it supports tool discovery, readiness checks, and detailed tool information, making it easier to scale tool access across multiple providers and bundles.