plugged.in MCP Proxy Server
@VeriTeknik
About plugged.in MCP Proxy Server
Plugged.in MCP Server manages all your other MCPs in one MCP.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"pluggedin-mcp-proxy": {
"command": "npx",
"args": [
"-y",
"@pluggedin/pluggedin-mcp-proxy@latest",
"--pluggedin-api-key",
"YOUR_API_KEY"
]
}
}
}Tools
23Get started with Plugged.in MCP - shows setup instructions and API key configuration (no API key required)
Triggers discovery of tools (and resources/templates) for configured MCP servers in the Pluggedin App.
Ask questions and get AI-generated answers from your knowledge base. Returns structured JSON with answer, document sources, and metadata.
Create and save AI-generated documents to the user's library in Plugged.in (requires API key)
List documents with filtering options from the user's library (requires API key)
Search for specific documents in your library. Returns document metadata (ID, title, snippet). To retrieve full content, use pluggedin_get_document with the returned document ID.
Retrieve a specific document's full content by ID. Use this after pluggedin_search_documents to get the complete content of documents you found. Set includeContent=true to get the full text.
Update or append to an existing AI-generated document (requires API key)
Send custom notifications through the Plugged.in system with optional email delivery. You can provide a custom title or let the system use a localized default.
List notifications from the Plugged.in system with optional filters for unread only and result limit
Mark a notification as done in the Plugged.in system
Delete a notification from the Plugged.in system
Set a clipboard entry by name (semantic key) or index (array-like). Named entries are upserted; indexed entries fail if index exists. Max 2MB per entry.
Get clipboard entries. Specify name or idx for a single entry, or omit both to list all entries with pagination.
Delete clipboard entries by name, index, or clear all entries.
List all clipboard entries with metadata. Image values are truncated to first 1000 chars for preview.
Push a value to the indexed clipboard with auto-incrementing index. Useful for building ordered pipelines or stack-like operations.
Pop the highest-indexed entry from the clipboard (LIFO behavior). Returns the entry value and removes it.
Start a new memory session to begin capturing observations. Returns a session UUID and memory_session_id for subsequent operations.
End a memory session and trigger Z-report generation (AI-compressed session summary).
Record an observation during a memory session. Observations are classified by the Analytics Agent into memory ring types (procedures, practice, longterm, shocks).
Search memories using semantic similarity. Returns lightweight results (50-150 tokens each) for token-efficient progressive disclosure. Use pluggedin_memory_details for full content.
Get full details for selected memories (progressive disclosure Layer 3). Use after pluggedin_memory_search to retrieve complete content for specific memories.
Overview
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.
Frequently asked questions
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.
Basic information
More Other MCP servers
IDA Pro MCP
mrexodiaAI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Codelf
unbugA search tool helps dev to solve the naming things problem.
🚀 Model Context Protocol (MCP) Curriculum for Beginners
microsoftThis open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,
Blender
ahujasidOpen-source MCP to use Blender with any LLM
Activepieces
activepiecesAI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
Comments