MCP Catalogs
Home

agent

by 1mcp-app·438·Score 52

1MCP is a unified MCP runtime that aggregates multiple MCP servers into one, offering CLI mode for progressive tool discovery.

developer-toolsai-llmproductivity
47
Forks
10
Open issues
this month
Last commit
2d ago
Indexed

Overview

1MCP addresses MCP configuration sprawl by providing a unified runtime that can aggregate multiple MCP servers behind a single endpoint. It offers multiple modes of operation including CLI mode for progressive discovery, stdio proxy for maximum compatibility, and direct HTTP attachment for native MCP clients. The implementation supports static servers loaded at startup and template servers resolved from client context, with features like async loading, instruction aggregation, and preset filtering. This makes it ideal for managing complex MCP setups across different AI agents while maintaining a consistent runtime experience.

Try asking AI

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

you:Giving coding agents a stable runtime with a smaller working surface
you:Sharing the same MCP inventory across Cursor, Claude Code, Codex, and internal tools
you:Exposing context-specific template servers per repository, branch, or session
you:What's the difference between CLI mode and stdio proxy mode?
you:How does 1MCP handle authentication?

When to choose this

Choose 1MCP when you need to manage multiple MCP servers across different clients while maintaining a single configuration and reducing each agent's initial tool surface.

When NOT to choose this

Avoid 1MCP if you need minimal overhead or are building a simple MCP setup with only one or two servers, as it adds a layer of complexity that may not be necessary.

Tools this server exposes

6 tools extracted from the README
  • instructions

    Get current runtime instructions and recommended workflow

  • inspect

    Discover servers or tools in the runtime

  • run

    Execute a specific tool with arguments

  • query-docs

    Query documentation from a library

  • proxy

    Start a stdio proxy for maximum client compatibility

  • mcp

    Manage MCP servers and connections

Note: Tool names extracted from CLI examples and documentation. This appears to be a meta-server that aggregates other MCP servers rather than exposing its own tools directly.

Comparable tools

mcp-server-aggregatormcp-proxymcp-unified

Installation

Installation

  1. Install 1MCP globally:
npm install -g @1mcp/agent
  1. Add upstream MCP servers:
1mcp mcp add context7 -- npx -y @upstash/context7-mcp
  1. Start the runtime:
1mcp serve

For Claude Desktop, add to claude_desktop_config.json:

{
  "mcpServers": {
    "1mcp": {
      "url": "http://127.0.0.1:3050/mcp?app=claude-code"
    }
  }
}

FAQ

What's the difference between CLI mode and stdio proxy mode?
CLI mode is designed for agent-style sessions with progressive discovery using 'instructions -> inspect -> run'. Stdio proxy mode offers broader client compatibility while maintaining project context through .1mcprc configuration.
How does 1MCP handle authentication?
1MCP supports authentication at the runtime level, with centralized auth configuration that applies to all aggregated MCP servers. See the authentication documentation for setup details.

Compare agent with

GitHub →

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