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

# Connect ChatGPT to the Operata MCP server

> What's needed for ChatGPT to connect to the Operata MCP Server, and what's pending on the OAuth side.

ChatGPT support for the Operata MCP Server is pending. The integration depends on an OAuth 2.0 flow on the Operata side; today the Operata MCP Server only accepts Bearer-token authentication, which ChatGPT's MCP (Model Context Protocol) client does not support.

## How it works

The Operata MCP Server exposes a [suite of tools](/docs/guides-mcp-tools) — schema discovery, trace search and analytics, and knowledge-base lookup — over HTTPS with Bearer-token authentication. Claude Desktop, Claude Code, the Claude API, and Cursor all accept Bearer tokens through their MCP configuration and connect against the existing endpoint. ChatGPT's MCP client requires OAuth 2.0; until Operata exposes an OAuth-authenticated endpoint, ChatGPT cannot connect.

The planned approach, per the [MCP Authorization Specification](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization#2-1-overview), is OAuth 2.0 with Auth0 fronting Operata user accounts. The same Operata user identity that signs in to the console authorizes ChatGPT to call the MCP server on their behalf.

## Related

* [Connect Claude to the Operata MCP server](/docs/guides-mcp-claude) — the working integration today.
* [Connect Cursor to the Operata MCP server](/docs/guides-mcp-cursor) — the working integration today.
* [Authentication](/docs/api-authentication) — the Bearer-token model the other MCP integrations use.
* [Rate limits](/docs/api-rate-limits) — the per-token budget that applies to MCP calls.