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

# AI gateways and MCP registries

> Register the Consensus MCP server in the gateway your organization already runs. The same five facts work everywhere; product pages give the exact field names.

If your organization routes AI traffic through a gateway or MCP registry, register Consensus there once and every agent behind it gets the `search` tool. Consensus is a plain remote Streamable HTTP server, so any product that can proxy a remote MCP server can front it.

## What every gateway needs

| Field                   | Value                                                                                             |
| ----------------------- | ------------------------------------------------------------------------------------------------- |
| Server URL              | `https://mcp.consensus.app/mcp`                                                                   |
| Transport               | Streamable HTTP (choose it explicitly; there is no SSE endpoint)                                  |
| Sessions                | None required. The server is stateless.                                                           |
| Auth, shared credential | Header `Authorization`, value `Bearer ak_live_...`                                                |
| Auth, per user          | OAuth 2.0 authorization code + PKCE (S256), scope `search`, Dynamic Client Registration supported |
| Discovery               | `https://consensus.app/.well-known/oauth-authorization-server`                                    |

Full details, including the firewall allowlist, are in the [connection reference](/enterprise/connection-reference).

## Which auth mode to pick

* **Shared API key** is the lowest-friction path and works with every product below. Everyone behind the gateway shares one Consensus account and its Enterprise limits.
* **Per-user OAuth** gives each person their own Consensus account and usage. Products marked "DCR" below can register themselves automatically; products marked "client ID/secret" need a confidential client, which Consensus provisions on request.

## Product guides

<CardGroup cols={2}>
  <Card title="TrueFoundry" href="/enterprise/gateways/truefoundry">API key · OAuth with client ID/secret</Card>
  <Card title="LiteLLM" href="/enterprise/gateways/litellm">Bearer · OAuth with DCR</Card>
  <Card title="Cloudflare MCP Server Portals" href="/enterprise/gateways/cloudflare">Bearer · OAuth with DCR</Card>
  <Card title="IBM ContextForge" href="/enterprise/gateways/ibm-contextforge">Bearer · OAuth with DCR</Card>
  <Card title="Azure API Management" href="/enterprise/gateways/azure-api-management">Bearer · OAuth with client ID/secret</Card>
  <Card title="AWS Bedrock AgentCore Gateway" href="/enterprise/gateways/aws-agentcore">API key · OAuth with client ID/secret</Card>
  <Card title="Portkey" href="/enterprise/gateways/portkey">Headers · OAuth with DCR</Card>
  <Card title="Obot" href="/enterprise/gateways/obot">Headers · OAuth with DCR</Card>
  <Card title="Kong, agentgateway, Zuplo, Docker, Boomi" href="/enterprise/gateways/other-gateways">Work with caveats</Card>
</CardGroup>

Don't see your platform? Any gateway that supports remote Streamable HTTP servers with a static bearer header will work with the table above. If you'd like us to verify a setup or add a guide, [contact sales](https://consensus.app/home/contact/sales/).