MCP Proxy Server that aggregates multiple MCP servers (STDIO, SSE, Streamable HTTP) and provides a unified interface with security, workspace management and real-time notifications.
https://github.com/VeriTeknik/pluggedin-mcp-proxyIf you're running more than a few MCP servers, you know the drill: cluttered client configs, namespace conflicts, and the constant dance of enabling/disabling servers depending on your current project. The plugged.in MCP Proxy eliminates this complexity by giving you a single entry point to all your MCP tools.
Most developers start with one MCP server, then two, then suddenly you're managing configurations for filesystem access, database connections, API integrations, and development tools across multiple clients. Your Claude Desktop config becomes a mess of server definitions, each with their own authentication, and switching between different toolsets means constant reconfiguration.
Before:
{
"mcpServers": {
"filesystem": { "command": "...", "env": {...} },
"database": { "command": "...", "env": {...} },
"github": { "command": "...", "env": {...} },
"aws": { "command": "...", "env": {...} },
"slack": { "command": "...", "env": {...} }
// ... and 10 more servers
}
}
After:
{
"mcpServers": {
"pluggedin": {
"command": "npx",
"args": ["-y", "@pluggedin/mcp-proxy@latest"],
"env": { "PLUGGEDIN_API_KEY": "your-key" }
}
}
}
The proxy doesn't just forward requests—it intelligently manages your MCP ecosystem. Each server gets proper namespace prefixing, so github_create_issue and database_create_table coexist without conflicts. You get clean, organized tool lists that make sense.
Want to switch from your "development" toolset to your "production monitoring" workspace? One click in the plugged.in app, and your entire MCP environment changes without touching client configurations.
Unlike simple proxy solutions, this includes enterprise-grade security:
Run it how you need it:
STDIO Mode (default) - Perfect for direct client integration:
npx -y @pluggedin/mcp-proxy@latest --pluggedin-api-key YOUR_KEY
HTTP Server Mode - Great for team environments or web integration:
npx -y @pluggedin/mcp-proxy@latest --transport streamable-http --port 8080
Docker - Production deployments with minimal footprint:
docker run -d -p 12006:12006 \
-e PLUGGEDIN_API_KEY="your-key" \
pluggedin-mcp-proxy:latest --transport streamable-http
Here's where it gets practical. Instead of managing individual server lifecycles, you configure once and let the proxy handle discovery, health checks, and request routing. Your existing MCP clients (Claude, Cline, Cursor) see one stable interface while your actual server infrastructure can change underneath.
Need to add a new API integration? Add it to your plugged.in workspace—no client reconfiguration needed. Want to test a new tool without breaking your existing setup? Create a new workspace and switch seamlessly.
The companion plugged.in app gives you visual control over your entire MCP ecosystem. See which tools are available, test them interactively, manage authentication credentials, and organize different workspace configurations. It's like having a control panel for your AI toolchain.
npx -y @pluggedin/mcp-proxy@latest --pluggedin-api-key YOUR_KEYThe proxy discovers your configured servers automatically and presents them as a unified toolset. No more switching between different server configurations or managing individual connection states.
Quick test: Run the proxy and call pluggedin_discover_tools to see it automatically find and configure your available MCP servers. It's the kind of "just works" experience that makes you wonder why you were managing everything manually before.
If you're running multiple MCP servers and tired of configuration overhead, this proxy eliminates the complexity while adding the management features you actually need.