Connect your agent

The gateway speaks the Model Context Protocol over Streamable HTTP. Any MCP-capable agent — Claude, ChatGPT, or your own — can use it. You bring the agent; we bring the data.

Two ways to connect

Federated endpoint — one connection, every data service you're entitled to. Tools are namespaced <service>_<tool> (e.g. stats_get_indicator).

Per-service endpoints — a smaller, focused tool list for a single service: https://mcp.unescap.org/api/mcp/<service>. Each catalog entry shows its own copy-paste instructions.

Access tiers & API keys

Public services work without credentials, subject to strict anonymous rate limits. Authorized services require an API key (Authorization: Bearer escap_…, an x-api-key header, or ?api_key= for connectors that can't set headers). Keys carry a tier, optional service allowlist, and per-minute/per-day quotas.

To request a key, contact the ESCAP MCP Gateway team with your name, organization and intended use. Keys are issued individually and can be revoked at any time.

Rate limits & errors

• Over-limit requests get HTTP 429 with a Retry-After header — well-behaved agents back off automatically.
• Missing or invalid keys get HTTP 401; data-service outages surface as JSON-RPC errors naming the affected service.
• The gateway is stateless: no sessions, no cookies — every request stands alone.

Try it

The MCP Inspector is the quickest smoke test: