home / mcp / agent mcp server

Agent MCP Server

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

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "1mcp-app-agent": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/context7-mcp"
      ]
    }
  }
}

You run a single, unified MCP server that aggregates multiple MCP backends into one entry point. This simplifies connecting clients and AI assistants to diverse MCP services while providing centralized configuration, security, and health monitoring.

How to use

Start the unified MCP server and configure the clients you want to connect. You add individual MCP backends as subserves, then run a single process that forwards requests, handles authentication, and provides a consistent endpoint for your assistants.

How to install

Prerequisites: you need Node.js environment or a binary installer depending on how you want to run the server.

Install the server using the binary option (recommended for environments without Node.js):

# Linux/macOS
curl -L https://github.com/1mcp-app/agent/releases/latest/download/1mcp-linux-x64.tar.gz | tar -xz
sudo mv 1mcp /usr/local/bin/

# Windows (PowerShell)
Invoke-WebRequest -Uri "https://github.com/1mcp-app/agent/releases/latest/download/1mcp-win32-x64.zip" -OutFile "1mcp.zip"
Expand-Archive -Path "1mcp.zip" -DestinationPath "."

Or run via NPM using the CLI helper:

npx -y @1mcp/agent --help

Add the MCP backends you want to aggregate. Each backend is registered as a separate MCP source that the unified server will manage.

1mcp mcp add context7 -- npx -y @upstash/context7-mcp
1mcp mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem ~/Documents

Start the unified MCP server:

1mcp

Additional sections

Configuration, security, and operational notes help you keep your setup stable and secure.

Configuration and security

The server acts as a proxy that manages and aggregates multiple MCP backends. It starts and stops these backends as subprocesses and forwards requests from AI assistants to the appropriate backend. Use the following configuration to register MCP backends and specify how the server should start each backend.

Troubleshooting and notes

If you encounter issues, verify that each MCP backend is reachable from the unified server, and check health endpoints for status information. Ensure that your tooling environment has the required permissions to start subprocesses and access network resources.

Available tools

startServer

Launch the unified MCP server process that manages and exposes a single MCP endpoint for all registered backends.

addMcpServer

listServers

List all MCP backends currently configured in the unified server.

serverStatus

Query health and status details for the unified MCP server and its registered backends.

authenticate

Provide OAuth 2.1 based authentication and scope-based authorization for client requests.