> ## Documentation Index
> Fetch the complete documentation index at: https://docs.portkey.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Catalog

> Every MCP server your organisation has approved, and who is allowed to call which tools.

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.

<Info>
  **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.
</Info>

<CardGroup cols={2}>
  <Card title="MCP Registry" icon="list" href="/docs/aigw/product/mcp-gateway/mcp-registry">
    Add servers, configure authentication, and see connection health
  </Card>

  <Card title="Quickstart" icon="rocket" href="/docs/aigw/product/mcp-gateway/quickstart">
    New to the MCP Gateway? Add your first server in five minutes.
  </Card>
</CardGroup>

## What can go in the catalog

<CardGroup cols={2}>
  <Card title="Internal MCP Servers" icon="building" href="/docs/aigw/product/mcp-gateway/internal-mcp-servers">
    Servers your organisation hosts
  </Card>

  <Card title="External MCP Servers" icon="globe" href="/docs/aigw/product/mcp-gateway/external-mcp-servers">
    Third-party servers reached over HTTP
  </Card>
</CardGroup>

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.

<CardGroup cols={2}>
  <Card title="Access Control" icon="user-lock" href="/docs/aigw/product/mcp-gateway/access-control">
    Which workspaces and users can reach a server
  </Card>

  <Card title="Tool Provisioning" icon="screwdriver-wrench" href="/docs/aigw/product/mcp-gateway/tool-provisioning">
    Which tools within a server they may call
  </Card>
</CardGroup>

## Related

* [Registry API](/docs/aigw/product/mcp-gateway/registry-api) — serve this catalog to governance-aware MCP clients as standard `server.json`
* [Advanced Configuration](/docs/aigw/product/mcp-gateway/advanced-configuration) — per-server tuning
* [MCP Gateway](/docs/aigw/product/mcp-gateway) — authentication, authorisation, guardrails, and observability for MCP traffic


## Related topics

- [MCP Registry](/docs/aigw/product/mcp-gateway/mcp-registry.md)
- [Open Library MCP server](/docs/aigw/integrations/mcp-servers/open-library-mcp-server.md)
- [Registry API (Beta)](/docs/aigw/product/mcp-gateway/registry-api.md)
- [LLM Catalog](/docs/aigw/product/catalogs/llms.md)
- [Agent Catalog](/docs/aigw/product/catalogs/agents.md)