> ## 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.

# Obot MCP Gateway

> Add the Consensus MCP server to Obot as a remote server with custom headers or spec-compliant per-user OAuth.

Obot is an open-source MCP gateway and registry with per-user OAuth, a catalog, and audit logging. Every server it exposes is served as `streamable-http` at `https://<your-obot>/mcp-connect/<server-id>`.

## Register the server

<Steps>
  <Step title="Add a remote server">
    Go to **MCP Management › MCP Servers**, select **Add MCP Server**, and choose the **Remote** type.
  </Step>

  <Step title="Set the URL">
    **Remote URL**: `https://mcp.consensus.app/mcp`. Optionally restrict connections to the hostname `mcp.consensus.app`.
  </Step>
</Steps>

## Authentication

<Tabs>
  <Tab title="Headers (shared or per user)">
    Add a header with **Key** `Authorization` and **Value** `Bearer ak_live_...`, and mark it **Sensitive**. Set the value to **User-Supplied** instead if each user should enter their own Consensus key.
  </Tab>

  <Tab title="OAuth (per user)">
    Nothing to configure. Consensus follows the MCP authorization spec with Dynamic Client Registration, which Obot supports out of the box; users sign in on first use. If you'd rather use a confidential client, enter the **Client ID** and **Client Secret** under static OAuth.
  </Tab>
</Tabs>

## Notes

* Remote servers configured for static OAuth without credentials are hidden from non-admin users.
* Servers using static OAuth can't be included in composite servers.

Obot docs: [MCP servers](https://docs.obot.ai/functionality/mcp-servers/) · [OAuth configuration](https://docs.obot.ai/configuration/mcp-server-oauth-configuration/)