Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@pluggedin/pluggedin-mcp-proxy) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

PluggedinMCP MCP Server

https://plugged.in: The One MCP to manage all your MCPs

PluggedinMCP MCP Server is a proxy server that joins multiple MCP⁠ servers into one. It fetches tool/prompt/resource configurations from PluggedinMCP App⁠ and routes tool/prompt/resource requests to the correct underlying server.

PluggedinMCP App repo: https://github.com/VeriTeknik/pluggedin-app

Key Features

MCP Playground: Interactive environment to test and experiment with your MCP tools
Multi-Server Support: Connect both STDIO (command-line) and SSE (HTTP-based) MCP servers
Custom MCP Servers: Create and manage your own Python-based MCP servers
Multi-Workspace Layer: Switch between different sets of MCP configurations with one click
Namespace Isolation: Keep joined MCPs separate and organized
LLM Integration: Seamless integration with OpenAI and Anthropic models
Real-time Updates: GUI dynamic updates of MCP configurations
Universal Compatibility: Works with any MCP client

Installation

Installing via Smithery

Sometimes Smithery works (confirmed in Windsurf locally) but sometimes it is unstable because PluggedinMCP is special that it runs other MCPs on top of it. Please consider using manual installation if it doesn't work instead.

To install PluggedinMCP MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @VeriTeknik/pluggedin-mcp-proxy --client claude

Manual Installation

export PLUGGEDIN_API_KEY=<env>
npx -y @pluggedin/pluggedin-mcp-proxy@latest

{
  "mcpServers": {
    "PluggedinMCP": {
      "command": "npx",
      "args": ["-y", "@pluggedin/pluggedin-mcp-proxy@latest"],
      "env": {
        "PLUGGEDIN_API_KEY": "<your api key>"
      }
    }
  }
}

Environment Variables

PLUGGEDIN_API_KEY: Required. Obtained from PluggedinMCP App's "API Keys" page (https://plugged.in/api-keys).
PLUGGEDIN_API_BASE_URL: Optional override for PluggedinMCP App URL (e.g. http://localhost:12005).

Command Line Arguments

You can configure the API key and base URL using command line arguments:

npx -y @pluggedin/pluggedin-mcp-proxy@latest --pluggedin-api-key <your-api-key> --pluggedin-api-base-url <base-url>

For help with all available options:

npx -y @pluggedin/pluggedin-mcp-proxy@latest --help

These command line arguments take precedence over environment variables.

Architecture Overview

sequenceDiagram
    participant MCPClient as MCP Client (e.g. Claude Desktop)
    participant PluggedinMCP-mcp-server as PluggedinMCP MCP Server
    participant PluggedinMCPApp as PluggedinMCP App
    participant MCPServers as Installed MCP Servers in Plugged.in App

    MCPClient ->> PluggedinMCP-mcp-server: Request list tools
    PluggedinMCP-mcp-server ->> PluggedinMCPApp: Get tools configuration & status
    PluggedinMCPApp ->> PluggedinMCP-mcp-server: Return tools configuration & status

    loop For each listed MCP Server
        PluggedinMCP-mcp-server ->> MCPServers: Request list_tools
        MCPServers ->> PluggedinMCP-mcp-server: Return list of tools
    end

    PluggedinMCP-mcp-server ->> PluggedinMCP-mcp-server: Aggregate tool lists
    PluggedinMCP-mcp-server ->> MCPClient: Return aggregated list of tools

    MCPClient ->> PluggedinMCP-mcp-server: Call tool
    PluggedinMCP-mcp-server ->> MCPServers: call_tool to target MCP Server
    MCPServers ->> PluggedinMCP-mcp-server: Return tool response
    PluggedinMCP-mcp-server ->> MCPClient: Return tool response

Credits

Forked from https://github.com/metatool-ai/mcp-server-metamcp
Inspirations and some code (refactored in this project) from https://github.com/adamwattis/mcp-proxy-server/