MCP Catalogs
Home

1mcp

by slzcdhd·1·Score 33

1mcp is a central proxy server that aggregates multiple MCP servers into a unified interface.

developer-toolsops-infraother
0
Forks
0
Open issues
10 mo ago
Last commit
2d ago
Indexed

Overview

1mcp provides a streamlined solution for managing multiple MCP servers by acting as a central proxy. It automatically discovers and aggregates tools, resources, and prompts from upstream servers, providing transparent routing based on prefixed capability names. The server supports multiple downstream clients simultaneously and features automatic reconnection, real-time updates, fast startup mode, and dynamic configuration hot-reloading without server restarts.

Try asking AI

After installing, here are 6 things you can ask your AI assistant:

you:Organizing multiple MCP servers into a single endpoint for client applications
you:Distributing MCP capabilities across different physical machines or environments
you:Providing failover and load balancing for MCP server clusters
you:How do I add a new MCP server to the proxy?
you:What transport protocols are supported for upstream servers?
you:Can the proxy handle downstream client disconnections?

When to choose this

Choose 1mcp when you need to manage multiple MCP servers and provide a unified interface to clients, especially when working with diverse transports or requiring dynamic configuration updates.

When NOT to choose this

Avoid 1mcp for simple use cases with only one MCP server, or if you need fine-grained control over individual server configurations as the abstraction might limit customization options.

Tools this server exposes

6 tools extracted from the README
  • tools/list

    List all available tools from aggregated upstream servers

  • tools/call

    Execute a specific tool from any connected upstream server

  • resources/list

    List all available resources from aggregated upstream servers

  • resources/read

    Read a specific resource from any connected upstream server

  • prompts/list

    List all available prompts from aggregated upstream servers

  • prompts/get

    Retrieve a specific prompt from any connected upstream server

Note: Tool names were inferred from the MCP protocol methods described in the README. The server acts as a proxy and exposes tools from upstream servers with prefixed names (serverName___toolName), but the specific tool names vary based on connec

Comparable tools

mcp-server-proxymcp-aggregatormulti-mcp-gatewaymcp-hub

Installation

Installation

Prerequisites

  • Node.js 18+
  • npm or yarn

Setup

  1. Clone and install dependencies:
git clone <repository-url>
cd 1mcp
npm install
  1. Build the project:
npm run build
  1. Create configuration file:
cp config/mcp_servers.json.example config/mcp_servers.json
  1. Start the server:
npm start

Claude Desktop Configuration

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "1mcp": {
      "command": "node",
      "args": ["<path-to-1mcp>/dist/main.js"],
      "env": {
        "CONFIG_PATH": "<path-to-config>/mcp_servers.json"
      }
    }
  }
}

FAQ

How do I add a new MCP server to the proxy?
Simply add the server configuration to mcp_servers.json and save the file. The proxy will automatically detect the change and connect to the new server without restarting.
What transport protocols are supported for upstream servers?
1mcp supports stdio (default), SSE (Server-Sent Events), streamable-http, and auto-detection for connecting to upstream servers.
Can the proxy handle downstream client disconnections?
Yes, the proxy manages client sessions with automatic cleanup. After 30 minutes of inactivity, sessions are automatically cleaned up.

Compare 1mcp with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.