PluggedinMCP

Name: PluggedinMCP
Author: VeriTeknik

@VeriTeknik

代码仓库

关于 PluggedinMCP

暂无概览

#mcp #proxy #middleware

基本信息

分类

其他

传输方式

stdio

发布者

VeriTeknik

提交者

Cem Karaca

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

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

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is PluggedinMCP?

PluggedinMCP is a middleware proxy that aggregates multiple MCP servers into a single unified interface. It fetches tool, prompt, and resource configurations from the plugged.in App and routes requests to the appropriate underlying servers for any MCP client like Claude Desktop, Cline, or Cursor.

How to use PluggedinMCP?

Install and run with npx -y @pluggedin/mcp-proxy@latest --pluggedin-api-key YOUR_API_KEY. Then configure your MCP client (e.g., Claude Desktop, Cline, Cursor) to use the proxy as a server, setting the PLUGGEDIN_API_KEY environment variable or via command-line argument. Docker builds are also supported.

Key features of PluggedinMCP

Aggregates multiple MCP servers into one interface
Supports both STDIO and WebSocket MCP servers
Keeps servers organized with namespace prefixing
Allows switching between workspace configurations
Fetches capabilities from plugged.in App APIs
Handles tools, resources, resource templates, and prompts

Use cases of PluggedinMCP

Manage multiple MCP servers from a single MCP client
Switch between different sets of MCP configurations per workspace
Test connected servers using MCP Inspector via Docker
Centralize API key and configuration management with the plugged.in App

FAQ from PluggedinMCP

What runtime does PluggedinMCP require?

Node.js 18+ is required (v20+ recommended).

How do I get an API key for the proxy?

Obtain an API key from the plugged.in App at https://plugged.in/api-keys.

Can PluggedinMCP be run with Docker?

Yes. Build the image with docker build -t pluggedin-mcp-proxy:latest . and run it with the required environment variables (PLUGGEDIN_API_KEY, PLUGGEDIN_API_BASE_URL).

Does the proxy support STDIO and WebSocket servers?

Yes, it supports both STDIO (command-line) and WebSocket (HTTP-based) MCP servers.

How does PluggedinMCP handle multiple servers?

It uses namespace isolation with prefixed names (e.g., tool names) and resolves calls to the appropriate underlying server via the plugged.in App API.