plugged.in MCP Proxy Server

What is plugged.in MCP Proxy Server?

A middleware that aggregates multiple Model Context Protocol (MCP) servers into a single unified interface. It fetches tool, prompt, and resource configurations from the plugged.in App and intelligently routes requests, providing built-in Knowledge (RAG v2), persistent Memory (clipboard system), Tools, and Proxy capabilities for any MCP client.

How to use plugged.in MCP Proxy Server?

Requires Node.js 18+ and an API key from plugged.in (get at plugged.in/api-keys). Install and run via npx -y @veriteknik/pluggedin-mcp. The proxy runs in STDIO mode by default or can be started as a Streamable HTTP server with optional Bearer token authentication. Configuration is managed through the plugged.in App, not local config files.

Key features of plugged.in MCP Proxy Server

• Built-in AI Playground to test MCPs without any client setup
• Universal MCP compatibility with Claude, Cline, Cursor, and more
• Multi-server support for STDIO, SSE, and Streamable HTTP servers
• Dual transport modes: STDIO (default) or Streamable HTTP
• RAG v2 document search with AI attribution and filtering
• Persistent clipboard memory system (set/get/push/pop operations)
• Notifications with optional email delivery and tracking
• Multi‑workspace layer to switch MCP configurations with one click

Use cases of plugged.in MCP Proxy Server

• Test and debug multiple MCP servers instantly from a single connection
• Give AI assistants document‑aware answers via built‑in RAG search
• Maintain long‑lived memory across AI sessions using the clipboard system
• Centralize MCP policies, telemetry, and authentication for enterprise clients

FAQ from plugged.in MCP Proxy Server

What are the technical prerequisites?

Node.js 18+ (recommended v20+). An API key from plugged.in App is required to fetch configurations and use the hub features.

How does this differ from connecting directly to MCP servers?

The proxy aggregates multiple MCP servers into one unified connection, adding built‑in tools (discovery, RAG, notifications, clipboard memory) and central management through the plugged.in App.

What transports does the proxy support?

Downstream: STDIO, SSE, and Streamable HTTP. Upstream: the proxy itself can run as STDIO (default) or Streamable HTTP server with optional API authentication and stateless mode.

Does the clipboard memory persist across sessions?

Yes. Clipboard entries are scoped to profiles/workspaces in the plugged.in App and survive session boundaries. Entries can be set by name or index, pushed/popped as a stack, and listed with metadata.

Can I use this with Claude Desktop or Cursor?

Yes. It works with any MCP client, including Claude Desktop, Cline, Cursor, and MCP Inspector, by pointing the client’s MCP configuration to the proxy’s STDIO or Streamable HTTP endpoint.