Skip to main content
The MCP catalog is the MCP Registry: the central list of every MCP server integration in your organisation. Organisation admins add servers here, configure how the AI Gateway authenticates to them, and control which teams can reach them.
Developer note: Most developers won’t add servers here. After an org admin provisions a server, use it from the workspace MCP page to copy the connection URL and test tools.

MCP Registry

Add servers, configure authentication, and see connection health

Quickstart

New to the MCP Gateway? Add your first server in five minutes.

​
What can go in the catalog

Internal MCP Servers

Servers your organisation hosts

External MCP Servers

Third-party servers reached over HTTP
The AI Gateway supports remote MCP servers over HTTP. Local STDIO servers need to be exposed as HTTP endpoints first.

​
Governing access

Registering a server is only half of it. Access control decides which teams reach which servers, and tool provisioning narrows that to individual tools.

Access Control

Which workspaces and users can reach a server

Tool Provisioning

Which tools within a server they may call
  • Registry API — serve this catalog to governance-aware MCP clients as standard server.json
  • Advanced Configuration — per-server tuning
  • MCP Gateway — authentication, authorisation, guardrails, and observability for MCP traffic
Last modified on September 15, 2026