Pluggedin

🚀 plugged.in MCP Proxy Server

The plugged.in MCP Proxy Server is a tool designed to bridge multiple Machine Conversation Protocol (MCP) servers, enabling MCP clients to discover and utilize features, resources, templates, and prompts across different MCP servers.

🚀 Quick Start

✨ Features

• Establishes a bridge between various MCP servers.
• Enables MCP clients to discover and use distributed features, resources, templates, and prompts.
• Integrates seamlessly with the pluggedin-app.
• Provides a web - based interface for MCP server configuration management.
• Supports centralized discovery of functions, custom instruction management, multi - workspace configuration, an interactive console for testing MCP tools, and user authentication and API key management.

📦 Installation

To install the plugged.in MCP Proxy Server, follow these steps:

git clone https://github.com/yourusername/pluggedin-mcp-proxy.git
cd pluggedin-mcp-proxy
npm install

Configuration

Create a config.json file and add the following content:

{
  "port": 3001,
  "appUrl": "http://localhost:3000",
  "servers": [
    {
      "name": "local-server",
      "host": "localhost",
      "port": 3002,
      "workspace": "default"
    },
    {
      "name": "remote-server",
      "host": "api.example.com",
      "port": 8080,
      "workspace": "production"
    }
  ]
}

🔧 Technical Details

Workflow

1. Configuration: The proxy server retrieves server configurations from the plugged.in application.
2. Function List: The proxy server fetches discovered functions via APIs:
   • tools/list: Obtained from /api/tools (returns prefixed names).
   • resources/list: Obtained from /api/resources.
   • resource-templates/list: Obtained from /api/resource-templates.
   • prompts/list: Merged results from /api/prompts and /api/custom-instructions.
3. Function Resolution: The proxy server resolves functions to target servers:
   • tools/call: Parses the prefix in the tool name and looks up the server in the internal mapping.
   • resources/read: Calls /api/resolve/resource?uri=... to get server details.
   • prompts/get: Checks for custom instruction prefixes or calls /api/resolve/prompt?name=....
4. Request Routing: Requests are routed to the appropriate underlying MCP servers.
5. Response Handling: Responses from the underlying servers are passed to the clients.

📚 Documentation

Integration with plugged.in Application

The plugged.in MCP Proxy Server is designed to integrate with the pluggedin-app, offering:

• A web - based application interface for managing MCP server configurations.
• Centralized discovery of features (tools, resources, templates, prompts).
• Custom instruction management.
• Support for multiple workspaces for different configuration sets.
• An interactive console for testing MCP tools.
• User authentication and API key management.

Related Resources

• pluggedin-app Repository
• Machine Conversation Protocol (MCP) Specification
• Claude Desktop Documentation
• Cline Documentation

Contribution

Contributions are welcome! Feel free to submit pull requests.

📄 License

This project is released under the MIT License. For detailed information, see the LICENSE file.