Navigation
1MCP: Unified AI Management & Seamless Scaling - MCP Implementation

1MCP: Unified AI Management & Seamless Scaling

1MCP unifies AI model management with seamless aggregation of multiple MCP servers, delivering a single, powerful platform for efficient scaling and simplified deployment.

Developer Tools
4.5(134 reviews)
201 saves
93 comments

Users create an average of 14 projects per month with this tool

About 1MCP

What is 1MCP: Unified AI Management & Seamless Scaling?

1MCP is a centralized server solution designed to streamline AI assistant workflows. It consolidates multiple Model Context Protocol (MCP) instances into a single interface, eliminating redundancy and simplifying configuration across tools like Claude Desktop, Cursor, and Cherry Studio. This unified platform ensures efficient resource utilization while maintaining compatibility with existing setups.

How to use 1MCP: Unified AI Management & Seamless Scaling?

Integrate 1MCP with existing AI tools in three steps:

  1. Launch the server with your preferred configuration:
    npx -y @1mcp/agent --config [PATH_TO_YOUR_CONFIG]
  2. Update client configurations to point to the 1MCP endpoint. For example, in Cursor's mcp.json:
    {
            "mcpServers": {
              "1mcp": {
                "type": "http",
                "url": "http://localhost:3050/sse"
              }
            }
          }
  3. Select transport protocols (SSE or stdio) and apply tag-based filtering to control server availability.

1MCP Features

Key Features of 1MCP: Unified AI Management & Seamless Scaling?

  • Centralized Control: Manage all MCP instances through one dashboard.
  • Resource Optimization: Reduce overhead by consolidating redundant server processes.
  • Dynamic Configuration: Reload settings without downtime using --config flags.
  • Tag-Based Filtering: Categorize servers by capabilities (e.g., network, filesystem) for granular access control.
  • Transport Flexibility: Switch between SSE for real-time communication or stdio for direct process integration.

Use Cases of 1MCP: Unified AI Management & Seamless Scaling?

1MCP excels in scenarios where multiple AI tools require seamless integration:

  • Consolidate MCP servers for teams using diverse AI assistants (e.g., Cursor for coding, Claude Desktop for writing).
  • Reduce infrastructure costs by eliminating duplicate server instances.
  • Automate tool switching via tags (e.g., route file operations to filesystem-tagged servers).
  • Enable real-time workflow updates without disrupting active sessions.

1MCP FAQ

FAQ from 1MCP: Unified AI Management & Seamless Scaling?

Q: Does 1MCP support existing MCP configurations?
Yes. Import configs from tools like Claude Desktop using the --config flag.

Q: How do I filter servers by capability?
Assign tags in your configuration and use the --tags flag or URL parameters (e.g., ?tags=network).

Q: Can I debug server interactions?
Use the MCP Inspector tool for real-time request tracing and debugging.

Q: What happens during a server shutdown?
1MCP gracefully terminates active processes and releases resources to prevent data loss.

Content

1MCP - One MCP Server for All

A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one.

Overview

1MCP (One MCP) is designed to simplify the way you work with AI assistants. Instead of configuring multiple MCP servers for different clients (Claude Desktop, Cherry Studio, Cursor, Roo Code, Claude, etc.), 1MCP provides a single, unified server that:

  • Aggregates multiple MCP servers into one unified interface
  • Reduces system resource usage by eliminating redundant server instances
  • Simplifies configuration management across different AI assistants
  • Provides a standardized way for AI models to interact with external tools and resources
  • Supports dynamic configuration reloading without server restart
  • Handles graceful shutdown and resource cleanup

Quick Start

To enable Cursor to use existing MCP servers already configured in Claude Desktop, follow these steps:

  1. Run the 1MCP server with the Claude Desktop config file:
npx -y @1mcp/agent --config ~/Library/Application\ Support/Claude/claude_desktop_config.json
  1. Add the 1MCP server to your Cursor config file (~/.cursor/mcp.json):
{
    "mcpServers": {
        "1mcp": {
            "type": "http",
            "url": "http://localhost:3050/sse"
        }
    }
}
  1. Enjoy it!

Usage

You can run the server directly using npx:

# Basic usage (starts server with SSE transport)
npx -y @1mcp/agent

# Use existing Claude Desktop config
npx -y @1mcp/agent --config ~/Library/Application\ Support/Claude/claude_desktop_config.json

# Use stdio transport instead of SSE
npx -y @1mcp/agent --transport stdio

# Show all available options
npx -y @1mcp/agent --help

Available options:

  • --transport, -t: Choose transport type ("stdio" or "sse", default: "sse")
  • --config, -c: Use a specific config file
  • --port, -P: Change SSE port (default: 3050)
  • --host, -H: Change SSE host (default: localhost)
  • --tags, -g: Filter servers by tags (see Tags section below)
  • --help, -h: Show help

Understanding Tags

Tags help you control which MCP servers are available to different clients. Think of tags as labels that describe what each server can do.

How to Use Tags

  1. In your server config : Add tags to each server to describe its capabilities
{
  "mcpServers": {
    "web-server": {
      "command": "uvx",
      "args": ["mcp-server-fetch"],
      "tags": ["network", "web"],
      "disabled": false
    },
    "file-server": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "~/Downloads"],
      "tags": ["filesystem"],
      "disabled": false
    }
  }
}
  1. When starting 1MCP in stdio mode : You can filter servers by tags
# Only start servers with the "network" tag
npx -y @1mcp/agent --transport stdio --tags "network"

# Start servers with either "network" or "filesystem" tags
npx -y @1mcp/agent --transport stdio --tags "network,filesystem"
  1. When using SSE transport : Clients can request servers with specific tags
{
    "mcpServers": {
        "1mcp": {
            "type": "http",
            "url": "http://localhost:3050/sse?tags=network"  // Only connect to network-capable servers
        }
    }
}

Example tags:

  • network: For servers that make web requests
  • filesystem: For servers that handle file operations
  • memory: For servers that provide memory/storage
  • shell: For servers that run shell commands
  • db: For servers that handle database operations

Configuration

Global Configuration

The server automatically manages configuration in a global location:

  • macOS/Linux: ~/.config/1mcp/mcp.json
  • Windows: %APPDATA%/1mcp/mcp.json

Configuration File Format

{
  "mcpServers": {
    "mcp-server-fetch": {
      "command": "uvx",
      "args": [
        "mcp-server-fetch"
      ],
      "disabled": false
    },
    "server-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "disabled": false
    }
  }
}

How It Works

System Architecture

graph TB
    subgraph "AI Assistants"
        A1[Claude Desktop]
        A2[Cursor]
        A3[Cherry Studio]
        A4[Roo Code]
    end

    subgraph "1MCP Server"
        MCP[1MCP Agent]
    end

    subgraph "MCP Servers"
        S1[Server 1]
        S2[Server 2]
        S3[Server 3]
    end

    A1 -->|sse| MCP
    A2 -->|sse| MCP
    A3 -->|sse| MCP
    A4 -->|sse| MCP

    MCP --> |sse| S1
    MCP --> |stdio| S2
    MCP --> |stdio| S3

Request Flow

sequenceDiagram
    participant Client as AI Assistant
    participant 1MCP as 1MCP Server
    participant MCP as MCP Servers

    Client->>1MCP: Send MCP Request
    activate 1MCP

    1MCP->>1MCP: Validate Request
    1MCP->>1MCP: Load Config
    1MCP->>MCP: Forward Request
    activate MCP

    MCP-->>1MCP: Response
    deactivate MCP

    1MCP-->>Client: Forward Response
    deactivate 1MCP

Development

Install dependencies:

pnpm install

Build the server:

pnpm build

For development with auto-rebuild:

pnpm watch

Run the server:

pnpm dev

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

pnpm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

Related MCP Servers & Clients