Server Aggregation

How MCP Gateway Pro combines multiple MCP servers into a single, unified endpoint.

The Challenge

As you add more MCP servers to your AI workflow, complexity grows:

  • Multiple connections to manage
  • Different authentication for each server
  • Tool name conflicts across servers
  • No unified view of available capabilities

How Aggregation Works

Your AI Application
Claude Desktop / Custom Agent
MCP Gateway Pro
Single Endpoint
github
neon
zapier
supabase
MCP Servers

The gateway maintains persistent connections to all your configured servers and presents them as a single unified MCP interface.

Automatic Namespacing

Different servers might have tools with the same name. For example, both GitHub and GitLab might have a list_repos tool.

The gateway automatically prefixes tool names with the server alias to prevent conflicts:

# Original tools from servers
GitHub:    list_repos, create_issue, get_me
Neon:      list_databases, run_query
Zapier:    list_zaps, trigger_zap

# Tools as seen through the gateway
github__list_repos
github__create_issue
github__get_me
neon__list_databases
neon__run_query
zapier__list_zaps
zapier__trigger_zap

The double underscore (__) separator makes it clear which server owns each tool while being easy to parse programmatically.

Request Routing

When your AI application calls a tool, the gateway:

  1. Parses the tool name - Extracts the server alias from the prefix
  2. Locates the server - Finds the connected server matching the alias
  3. Forwards the request - Sends the tool call with the original (unprefixed) name
  4. Returns the response - Passes the result back to your application

Example: When you call github__create_issue, the gateway calls create_issue on the GitHub server.

Listing All Tools

When you call tools/list, the gateway:

  1. Queries each connected server for its tools
  2. Prefixes each tool name with the server alias
  3. Combines all tools into a single response
{
  "jsonrpc": "2.0",
  "result": {
    "tools": [
      { "name": "github__get_me", "description": "Get authenticated user" },
      { "name": "github__list_repos", "description": "List repositories" },
      { "name": "neon__list_databases", "description": "List databases" },
      { "name": "neon__run_query", "description": "Execute SQL query" },
      { "name": "zapier__list_zaps", "description": "List your Zaps" }
    ]
  },
  "id": 1
}

Benefits

Simplified Configuration

One endpoint URL and one API key for all your servers.

No Conflicts

Automatic namespacing prevents tool name collisions.

Centralized Management

Add, remove, and update servers from the dashboard.

Unified Analytics

See usage across all servers in one place.