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

# Consensus for enterprise

> Consensus is used by some of the largest research organizations in the world through the MCP server and the API. Pick the deployment shape that fits your organization, then follow the guide for your platform.

Consensus is used by some of the largest research organizations in the world, connected through the [MCP server](/consensus-mcp) or the [API](/api-get-started). Both give your users search over 220 million peer-reviewed papers from inside the tools they already use. How you wire it up depends on your organization's requirements.

## Three ways to deploy

| Shape                         | How it works                                                                                                                                              | Best for                                                                                                            |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Per-user OAuth**            | Each person connects an MCP client (Claude, ChatGPT, Cursor, and others) and signs in to their own Consensus account. No admin work.                      | Teams that already run AI tools and want individual usage and limits.                                               |
| **Shared gateway credential** | Your AI gateway or MCP registry holds one Consensus API key server-side and proxies requests for everyone behind it. No user redirects, no token refresh. | Organizations that route all AI traffic through a gateway (TrueFoundry, LiteLLM, Azure API Management, and others). |
| **Microsoft 365 Copilot**     | An admin adds Consensus as a federated connector; users connect it under **Sources** in Copilot Chat.                                                     | Microsoft 365 shops where users can't add sources themselves.                                                       |

All three hit the same server, the same index, and the same [search tool](/consensus-mcp#search-tool). Mixing them is fine.

## Guides

<CardGroup cols={2}>
  <Card title="Connection reference" icon="file-code" href="/enterprise/connection-reference">
    Endpoint, transport, authentication options, discovery documents, and the firewall allowlist. Everything a gateway needs.
  </Card>

  <Card title="Microsoft 365 Copilot" icon="https://mintcdn.com/consensus-f7e6ffce/pL2GxbOkiUPczTU3/logo/clients/microsoft-copilot.svg?fit=max&auto=format&n=pL2GxbOkiUPczTU3&q=85&s=75c05e6833531f429009c4583d74c10c" href="/enterprise/microsoft-365-copilot" width="44" height="40" data-path="logo/clients/microsoft-copilot.svg">
    For admins: add Consensus as a federated connector so it appears in your users' Sources.
  </Card>

  <Card title="Microsoft Copilot Studio" icon="https://mintcdn.com/consensus-f7e6ffce/pL2GxbOkiUPczTU3/logo/clients/microsoft-copilot.svg?fit=max&auto=format&n=pL2GxbOkiUPczTU3&q=85&s=75c05e6833531f429009c4583d74c10c" href="/enterprise/copilot-studio" width="44" height="40" data-path="logo/clients/microsoft-copilot.svg">
    Add Consensus as a Model Context Protocol tool in your own agents.
  </Card>

  <Card title="AI gateways" icon="server" href="/enterprise/gateways/overview">
    Register Consensus in TrueFoundry, LiteLLM, Cloudflare, IBM ContextForge, Azure API Management, AWS AgentCore, Portkey, Obot, and more.
  </Card>

  <Card title="Security and data handling" icon="shield-check" href="/enterprise/security">
    SOC 2 Type II compliant. What leaves your network, what comes back, and what Consensus stores.
  </Card>
</CardGroup>

## Need help?

Enterprise plans include custom rate limits, page sizes up to 1,000 papers, DOIs and full-text excerpts in results, and setup support. Consensus is SOC 2 Type II compliant and supports SAML 2.0 single sign-on. To set up SSO, get a confidential OAuth client for your gateway, raise limits, or get help with a platform that isn't documented here, [talk to sales](https://consensus.app/home/contact/sales/).