unified-mcp-gateway

Route tool calls across multiple MCP servers through a unified gateway endpoint.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/tanujkumar38/unified-mcp-gateway --skill unified-mcp-gateway-tanujkumar38
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unified-mcp-gateway
Source: https://github.com/tanujkumar38/unified-mcp-gateway/tree/main/.agents/skills/unified-mcp-gateway
Command: npx skills add https://github.com/tanujkumar38/unified-mcp-gateway --skill unified-mcp-gateway-tanujkumar38

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Connecting AI agents to many MCP servers floods the context window with dozens of tool schemas and requires managing separate endpoints for each server. This Skill provides a single gateway that federates multiple MCP servers behind one endpoint and exposes lightweight meta-tools for dynamic tool discovery and routing. ## Core Features & Use Cases - Meta-Tool Routing: Discover, inspect, and call tools across all connected servers using four meta-tools (gateway_search_tools, gateway_get_tool_schema, gateway_call_tool, gateway_add_server) with under 200 prompt tokens of overhead. - Dynamic Server Registration: Add new MCP servers at runtime by SSE URL, npm package, or GitHub repository link without restarting the gateway. - Three Operating Modes: Choose meta mode for context-optimized agents, hybrid mode for production with ChatGPT connectors, or direct mode for full namespaced tool exposure. - Use Case: An agent needs to screen stocks and then generate a video summary. It searches the gateway for a screener tool, fetches its schema, executes it against the Tickertape server, then routes a video generation call to the Google Flow server, all through one SSE endpoint. ## Quick Start Connect your agent to the gateway SSE endpoint and ask it to search for the tool you need, fetch its schema, and execute it through the gateway.

Frequently Asked Questions about unified-mcp-gateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect multiple MCP servers to one AI agent?

Point your agent at the gateway's single SSE endpoint instead of configuring each server separately. The gateway federates all connected servers and exposes meta-tools to search, inspect, and call any upstream tool through one connection.

How to add a new MCP server without restarting the gateway?

Call the gateway_add_server meta-tool with a link to an SSE URL, npm package, or GitHub repository, plus an optional auth token. You can also POST the same payload to the /api/servers/add REST endpoint.

Does the gateway work with Claude Desktop and ChatGPT?

Yes. Claude Desktop connects via the remote SSE URL or a local stdio command in claude_desktop_config.json. ChatGPT Developer Mode connects by adding the SSE endpoint URL as a custom MCP server.

What is the difference between meta, hybrid, and direct gateway modes?

Meta mode exposes only four lightweight meta-tools to minimize prompt tokens. Hybrid adds ChatGPT search and fetch connectors plus direct aliases. Direct mode exposes all upstream tools with namespaced prefixes for large-context clients.

Why does the gateway report a degraded status for a server?

A degraded status means an upstream plugin is unreachable or missing a dependency, such as Google Flow lacking an attached Chrome instance on CDP port 9222. Check the /health endpoint for per-plugin status messages.