Skip to content

# Add pluggedin-mcp to Aggregators section #1371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ckaraca
Copy link

@ckaraca ckaraca commented Apr 11, 2025

Description

Add pluggedin-mcp-proxy to the MCP servers list. Plugged.in MCP Server is a comprehensive proxy server that combines multiple MCP servers into a single unified interface with extensive visibility features.

Server Details

  • Server: pluggedin-mcp-proxy
  • Changes to: Adding new server

Motivation and Context

Plugged.in MCP Server addresses the growing need for managing multiple MCP servers through a single interface. It provides enhanced visibility of prompts, resources, and templates across servers, plus a playground for debugging when building MCP servers. This addition will benefit the MCP community by offering a solution for developers working with multiple MCP implementations.

How Has This Been Tested?

The server has been tested with multiple MCP clients including Claude Desktop, Cursor, and Cline. Testing scenarios included:

  • Connecting multiple STDIO and WebSocket MCP servers
  • Cross-LLM testing using langchain-mcp-tools
  • Tool discovery and routing across servers
  • Collections management for different development environments

Breaking Changes

No breaking changes. This is a new server addition that doesn't affect existing functionality.

Types of changes

  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Plugged.in MCP Server features:

  • Universal MCP Compatibility with any MCP client
  • Multi-Server Support for both STDIO and WebSocket MCP servers
  • Namespace Isolation to keep joined MCPs separate and organized
  • Multi-Workspace Layer to switch between different sets of MCP configurations
  • Extensive visibility of prompts, resources, and templates
  • Playground for debugging with comprehensive logging capabilities
  • Collections creation for different clients
  • Cross-LLM testing capabilities using langchain-mcp-tools

The server is implemented in TypeScript and designed to run as a local service, making it suitable for developers who need to manage multiple MCP servers while maintaining privacy and control.

## Description
This PR adds the pluggedin-mcp to the Aggregators section. Plugged.in MCP Server acts as a proxy server that combines multiple MCP servers into a single unified interface with extensive visibility features. It fetches tool, prompt, and resource configurations from the plugged.in App and intelligently routes requests to the appropriate underlying MCP servers.

## Features
- Universal MCP Compatibility with any MCP client (Claude, Cline, Cursor, etc.)
- Multi-Server Support for both STDIO and WebSocket MCP servers
- Namespace Isolation to keep joined MCPs separate and organized
- Multi-Workspace Layer to switch between different sets of MCP configurations
- Extensive visibility of prompts, resources, and templates across all connected servers
- Discovery functionality to see details of available servers and tools
- Playground for extensive debugging when building MCP Servers
- Collections creation for different clients (Claude Desktop, Cursor, Cline)
- Tool Management across all connected MCP servers
- Intelligent Routing of tool calls to the appropriate underlying MCP server

## Checklist
- [x] The entry follows the repository's format
- [x] The description is concise and informative
- [x] The appropriate emojis are used (TypeScript, Local Service)
- [x] The GitHub repository link is valid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant