Skip to content
GridRouterhome

Search

Search providers, capabilities and pages

MCP server

An MCP server that gives agents every GTM data tool

Point any MCP client at one URL and your agent can search the catalog, get a quote and call any capability, inside the budget you set.

See it working

Agent calls in the call logDemo dataOpen in the demo
Calls over time291 calls, 90-minute buckets
  • Hit238
  • Miss51
  • Failed1
Calls per bucket by outcome
Bucket (UTC)HitMissFailed
Sep 27, 15:56 UTC730
Sep 27, 17:26 UTC730
Sep 27, 18:56 UTC1210
Sep 27, 20:26 UTC320
Sep 27, 21:56 UTC1100
Sep 27, 23:26 UTC400
Sep 28, 00:56 UTC310
Sep 28, 02:26 UTC400
Sep 28, 03:56 UTC500
Sep 28, 05:26 UTC100
Sep 28, 06:56 UTC210
Sep 28, 08:26 UTC210
Sep 28, 09:56 UTC810
Sep 28, 11:26 UTC400
Sep 28, 12:56 UTC1110
Sep 28, 14:26 UTC910
Sep 28, 15:56 UTC920
Sep 28, 17:26 UTC920
Sep 28, 18:56 UTC600
Sep 28, 20:26 UTC800
Sep 28, 21:56 UTC210
Sep 29, 00:56 UTC120
Sep 29, 02:26 UTC110
Sep 29, 03:56 UTC200
Sep 29, 05:26 UTC220
Sep 29, 06:56 UTC400
Sep 29, 08:26 UTC320
Sep 29, 09:56 UTC210
Sep 29, 11:26 UTC500
Sep 29, 12:56 UTC630
Sep 29, 14:26 UTC310
Sep 29, 15:56 UTC920
Sep 29, 17:26 UTC820
Sep 29, 18:56 UTC810
Sep 29, 20:26 UTC610
Sep 29, 21:56 UTC920
Sep 29, 23:26 UTC400
Sep 30, 00:56 UTC400
Sep 30, 02:26 UTC300
Sep 30, 03:56 UTC200
Sep 30, 05:26 UTC110
Sep 30, 06:56 UTC410
Sep 30, 08:26 UTC300
Sep 30, 09:56 UTC210
Sep 30, 11:26 UTC430
Sep 30, 12:56 UTC911
Sep 30, 14:26 UTC640
ProviderCallsError ratep95Spend
Example Alpha960.0%2993 ms$0.412
Example Zeta420.0%925 ms$0.0086
Example Gamma310.0%4557 ms$0.079
Example Beta240.0%1206 ms$0.014
Example Eta234.3%5308 ms$0.082
Example Sigma210.0%2455 ms$0.017
Example Delta200.0%2883 ms$0.0048
Example Theta110.0%4515 ms$0.029
Example Pi100.0%7394 ms$0.0024
Example Lambda90.0%727 ms$0.0014
Example Tau40.0%4527 ms$0
Calls from Claude Desktop and Cursor arrive over MCP and show up in the same log, charts and spend as API calls.

What you get

  • One server URL

    https://mcp.gridrouter.io/mcp over streamable HTTP, with OAuth or an API key.

  • Tools for the whole loop

    Search the catalog, quote a call, run a capability or a waterfall, and read a run's result.

  • Scoped keys and spend caps for agents

    Give each agent its own key with only the scopes it needs and a daily, weekly or monthly limit.

  • The same pipeline as the API

    MCP calls route, fall back, hit the private cache and land in the call log like any other call.

  • Your waterfalls become tools

    A published waterfall shows up as its own MCP tool, versioned like the endpoint.

How it works

  1. Create an API key for the agent with the call and catalog:read scopes and a spend limit.

  2. Add the GridRouter server to your MCP client's config.

  3. Ask for data in plain language; the agent picks the tool, and every call is logged.

mcp.json
{
  "mcpServers": {
    "gridrouter": {
      "url": "https://mcp.gridrouter.io/mcp",
      "headers": { "Authorization": "Bearer ${GRID_API_KEY}" }
    }
  }
}

Questions

Which MCP clients work?

Any client that speaks streamable HTTP MCP, including Claude Desktop, Claude Code and Cursor. Clients that support OAuth can sign in instead of pasting a key.

How do I stop an agent from overspending?

Give it its own API key with a spend limit that resets daily, weekly or monthly. Calls past the limit are refused before any provider is called.

Are MCP calls billed differently?

No. They're the same calls as the API, with the same prices, cache and logs.

Try it on your own data

Free while we launch. Bring your vendor keys; no card needed.