plugged.in MCP Proxy

Official

Unified MCP hub that aggregates all your MCP servers into one connection, with knowledge, memory, and tools.

Unverified

stdio (local)

API key

TypeScript

View repo 131 Website npm

Add to your client

Copy the config for your MCP client and paste it into its config file.

Install / run

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

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

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

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

Before you start

Node.js 18+ (v20+ recommended)
An API key from the plugged.in App (https://plugged.in/api-keys)

About plugged.in MCP Proxy

plugged.in MCP Proxy is a unified hub that aggregates multiple MCP servers behind one MCP connection. It fetches tool/prompt/resource configurations from the plugged.in App and routes requests to the correct underlying server, while adding built-in Knowledge (RAG v2 document search and creation), Memory (clipboard tools), and notification capabilities. It supports STDIO and Streamable HTTP transports and works with any MCP client.

Tools & capabilities (14)

pluggedin_discover_tools

Smart discovery of available tools with caching for instant results; supports force_refresh and per-server discovery via server_uuid.

pluggedin_ask_knowledge_base

RAG search across your documents with AI filtering capabilities.

pluggedin_send_notification

Send notifications with optional email delivery.

pluggedin_create_document

Create AI-generated documents in your library.

pluggedin_list_documents

List documents with filtering options.

pluggedin_search_documents

Search for specific documents by query.

pluggedin_get_document

Retrieve a specific document's full content by ID.

pluggedin_update_document

Update or append to an existing document.

pluggedin_clipboard_set

Set a clipboard entry by name (semantic key) or index.

pluggedin_clipboard_get

Get clipboard entries by name, index, or list all.

pluggedin_clipboard_delete

Delete clipboard entries by name, index, or clear all.

pluggedin_clipboard_list

List all clipboard entries with metadata.

pluggedin_clipboard_push

Push a value with an auto-incrementing index (stack push).

pluggedin_clipboard_pop

Pop the highest-indexed entry (LIFO behavior).

What this server can do

plugged.in MCP Proxy provides tools for these capabilities — tap one to see every MCP server that does the same:

Search documentation

When to use it

Manage and test all of your MCP servers from a single unified connection
Switch between different sets of MCP configurations (workspaces) with one click
Ground model outputs with RAG search across a unified, attribution-aware document library
Let MCP servers create, version, and manage documents with full model attribution
Persist working state across sessions using clipboard-style memory tools
Run the proxy as a remote Streamable HTTP server for web apps and hosted deployments

Security notes

Requires a PLUGGEDIN_API_KEY from the plugged.in App. The proxy validates commands against an allowlist (node, npx, python, python3, uv, uvx, uvenv), uses execFile() to avoid shell injection, sanitizes arguments and environment variables, and applies SSRF protection on URLs (blocking localhost, private IP ranges, and internal ports). In Streamable HTTP mode, enable --require-api-auth to require a Bearer token; rate limiting (60 tool calls/min, 100 API calls/min) and HTML/XSS sanitization are built in.

plugged.in MCP Proxy FAQ

Is this an MCP server or just a proxy?

It is an MCP server that acts as a hub/proxy: it exposes its own built-in tools (discovery, RAG/knowledge, notifications, document management, clipboard memory) and also aggregates and routes to the tools of any downstream MCP servers you've configured in the plugged.in App.

What transports are supported?

It runs as STDIO by default and can also run as a Streamable HTTP server (default port 12006) with optional Bearer-token authentication (--require-api-auth) and a stateless mode. Downstream servers may use STDIO, SSE, or Streamable HTTP.

Do I need an API key?

Yes. A PLUGGEDIN_API_KEY from the plugged.in App is required; the proxy fetches server configurations and discovered capabilities from the plugged.in App's APIs.

Which clients does it work with?

Any MCP client, including Claude Desktop, Cline, Cursor, and MCP Inspector. The README provides config blocks for Claude Desktop and Cline and command-line usage for Cursor.

#mcp-proxy #mcp-hub #aggregator #rag #memory #notifications #streamable-http #plugged.in

Alternatives to plugged.in MCP Proxy

Compare all alternatives →

Playwright MCP Server

Developer Tools

24k

Microsoft's official browser-automation MCP using Playwright's accessibility tree (no vision model).

Featured

Verified

stdio (local)

No auth

TypeScript

12 tools

Updated 13 days agoRepo

Context7 MCP Server

Developer Tools

28k

Up-to-date, version-specific library documentation injected into your coding agent.

Verified

stdio (local)

API key

TypeScript

2 tools

Updated 17 days agoRepo

Serena

Developer Tools

12k

LSP-powered coding agent toolkit: semantic symbol search, references and structural edits.

Verified

stdio (local)

No auth

Python

11 tools

Updated 15 days agoRepo

Compare plugged.in MCP Proxy with:

vs Playwright MCP Server vs Context7 MCP Server vs Serena vs Mobile MCP