MCP of Mcps
Merge every MCP server into one endpoint, and let tools pass data to each other without going through the model.Read full description
eliavamarLABSCO SUMMARY
A gateway trades a fixed tool list for one connection you can change without touching client config.
The appeal is obvious: enable a server in the dashboard and every client that already points here can use it, with no config edits and no restart. The trade is that the tool surface is never fixed, so there is no stable list to review before you connect. The one-time-token path is worth noting if you run headless agents, since it avoids storing a long-lived key next to the code.
What it is
A multi-tenant gateway rather than a single server. Agent Store's own catalogue reported 43 MCP servers and 225 tools running behind this one address on 16 August 2026, and what you see depends on what your account has enabled.
What you get
Whatever the servers you have enabled expose — the tool surface is not fixed, which is the point of a gateway. Across the whole catalogue, Agent Store counts 225 tools.
Requirements
An account, then one of three ways in: OAuth 2.1 with dynamic client registration, an X-API-Key header using an as_live_ key, or a one-time-token exchange for headless agents.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Connecting once instead of per server
Point the client at one URL and manage which servers are enabled from the dashboard rather than in every client's config file.
02
Giving a headless agent access safely
Exchange a one-time token instead of embedding a long-lived key in the deployment.
BEFORE YOU INSTALL
What to know first
Tools you get
225 tools by Agent Store's count.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1 (dynamic client registration supported), X-API-Key header (as_live_... format), or one-time-token (OTT) exchange for headless agents
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://agent.store/mcpRequirements
- OAuth 2.1 (dynamic client registration supported), X-API-Key header (<YOUR_API_KEY> format), or one-time-token (OTT) exchange for headless agents
