Pluggedin MCP Proxy

🚀 plugged.in Model Context Protocol (MCP) Proxy Server

The plugged.in MCP Proxy Server is designed to serve Model Context Protocol (MCP) clients, connecting to multiple underlying MCP servers and exposing their capabilities to upper - level applications through a unified interface.

🚀 Quick Start

The plugged.in MCP Proxy Server serves as an interface for MCP clients. It connects multiple underlying MCP servers and exposes their capabilities (tools, resources, prompts, etc.) to upper - level applications via a unified interface.

✨ Features

• Centralized Capability Discovery: Facilitates the discovery of tools, resources, templates, and prompts.
• Custom Instruction Management: Enables the management of custom instructions.
• Multi - Workspace Support: Allows for maintaining different configuration sets.
• Interactive Console: Provides an interactive console for testing MCP tools.
• User Authentication and API Key Management: Manages user authentication and API keys.

📦 Installation

1. Install Dependencies

Install Node.js

It is recommended to use Node.js version 16 or higher. You can install it using the following commands:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
nvm install --lts

Install npm Packages

npm install -g npm@latest

Install Project Dependencies

After entering the project directory, run:

npm install

2. Run the Server

Start the proxy server using the following command:

node index.js

Additional Installation Steps

Start the Development Server

npm run dev

Build the Project

npm run build

Run Tests

npm test

🔧 Technical Details

System Architecture

The proxy server acts as a bridge between MCP clients (such as Claude Desktop) and multiple underlying MCP servers.

Workflow

1. Configuration Retrieval: The proxy server retrieves server configuration from the plugged.in application.
2. Capability Listing:
   • tools/list: Get the tool list (with prefix) via the /api/tools interface.
   • resources/list: Get the resource list via the /api/resources interface.
   • resource - templates/list: Get the resource template list via the /api/resource - templates interface.
   • prompts/list: Combine the results from /api/prompts and /api/custom - instructions to return the prompt list.
3. Capability Resolution:
   • tools/call: Extract the prefix from the tool name to find the target server.
   • resources/read: Call the /api/resolve/resource?uri=... interface to get server details.
   • prompts/get: Check for custom instruction prefixes or call the /api/resolve/prompt?name=... interface.
4. Request Routing: Forward requests to the corresponding underlying MCP servers.
5. Response Handling: Return responses from the underlying servers to the client.

📚 Documentation

Integration with plugged.in Application

The proxy server is designed to work seamlessly with the [plugged.in application](https://github.com/VeriTeknik/pluggedin - app).

Related Resources

• [plugged.in Application Repository](https://github.com/VeriTeknik/pluggedin - app)
• Model Context Protocol (MCP) Specification
• [Claude Desktop Documentation](https://docs.anthropic.com/claude/docs/claude - desktop)
• Cline Documentation

Project Structure

• index.js: The main entry file to start the proxy server.
• config/: Contains configuration files and environment variable settings.
• routes/: Defines various HTTP route handling logics.
• middleware/: Implements middleware functions for request processing.
• utils/: Provides auxiliary functions and utility methods.

Contribution Guidelines

1. Clone the Repository

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

2. Install Dependencies

   npm install
   

3. Start the Development Environment

   npm run dev
   

4. Start Coding

   • Review the project structure and get familiar with the code organization.
   • Develop or fix issues for specific functional modules.

5. Commit Changes

   • After making modifications, add change records:

     git add .
     git commit -m "Your commit message"
     

   • Push to the remote repository:

     git push origin your - branch - name
     

6. Create a Pull Request

   • Create a new Pull Request for the project on GitHub, detailing the modifications you've made and their purposes.

Issue Reporting

If you encounter any issues or have suggestions for improvement, please visit the [Issues page](https://github.com/yourusername/pluggedin - mcp - proxy/issues) to submit an issue.

📄 License

This project is licensed under the MIT LICENSE.