Pluggedinmcp

🚀 plugged.in MCP Proxy Server

The plugged.in MCP proxy server serves as a universal bridge, connecting MCP clients to multiple underlying MCP servers. It simplifies client interactions with different servers and enables centralized management and discovery through the plugged.in application.

🚀 Quick Start

Basic Usage

1. Start the proxy server

   node index.js
   

2. Connect the MCP client

   npx @modelcontextprotocol/client --mcp-endpoint tcp://localhost:4000
   

Example Workflow

Discovery Tool

await client.call("pluggedin_discover_tools");
// Returns a list of discovered tools

✨ Features

• Simplified Interaction: Simplifies the interaction between clients and different MCP servers.
• Centralized Management: Enables centralized configuration and monitoring of all MCP servers through the plugged.in application.
• Multi - Workspace Support: Different workspaces can independently manage tools, resources, and instruction sets.
• Interactive Console: Allows users to test tool calls and view real - time logs.

📦 Installation

Clone the Repository

git clone git@github.com:vernit/pluggedin-mcp-proxy.git
cd pluggedin-mcp-proxy

Start Script (Docker)

# Dockerfile content
FROM node:18-alpine AS dev

WORKDIR /app
COPY package*.json ./
RUN npm install --production

CMD ["node", "index.js"]

Run the commands:

docker build -t pluggedin-mcp-proxy .
docker run -it pluggedin-mcp-proxy

🔧 Technical Details

Core Components

1. Proxy Server: Handles client requests and routes them to the target servers.
2. Capability Management:
   • tools/list: Retrieves a list of all tools.
   • resources/list: Retrieves a list of all resources.
3. Custom Instructions: Supports custom instructions based on prefixes.

Implementation Details

• The proxy server discovers new servers through the /api/discover endpoint.
• Each server gets a unique prefix during registration for request routing.

📚 Documentation

Integrating with the plugged.in Application

• Unified Management: Centrally configure and monitor all MCP servers through the plugged.in application.
• Multi - Workspace Support: Different workspaces can independently manage tools, resources, and instruction sets.
• Interactive Console: Test tool calls and view real - time logs.

Related Resources

• plugged.in Application Repository
• Machine Conversation Protocol (MCP) Specification
• Claude Desktop Documentation
• Cline Documentation

🤝 Contribution Guidelines

Contributions are welcome! Please feel free to submit a Pull Request.

📄 License

This project is licensed under the MIT License. See the LICENSE file for details.

🙏 Acknowledgments

• Inspired by MCP Proxy Server
• Built on Machine Conversation Protocol