How to add plugged.in MCP Proxy to Cursor

Unified MCP hub that aggregates all your MCP servers into one connection, with knowledge, memory, and tools. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 131★ · stdio · apikey · official

Cursor config for plugged.in MCP Proxy

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

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

Setup steps

1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
2Paste the plugged.in MCP Proxy config below into the "mcpServers" object.
3Fill in placeholder secrets, then save.
4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
5Ask Cursor to use one of plugged.in MCP Proxy's tools to confirm it's connected.

Before you start

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

What plugged.in MCP Proxy can do in Cursor

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.

Security

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 + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the plugged.in MCP Proxy config there under the "mcpServers" key and restart the client.

Is plugged.in MCP Proxy safe to use with Cursor?

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.

View repo Full plugged.in MCP Proxy page