Skip to main content
Connect ChatGPT to the Operata MCP Server as a custom connector so you can query your Operata data from a chat. ChatGPT connects over OAuth and signs in as your Operata user, so there’s no key to paste. ChatGPT uses OAuth only. Unlike Claude and Cursor, it has no API key path. For how OAuth, roles, and groups work, see the MCP overview.

​
Before you start

  • A ChatGPT Pro or Plus account. Custom connectors are a beta feature enabled through Developer Mode.
  • An Operata user with the Admin or User role. Viewer accounts and RBAC users can’t use the MCP Server. See Before you start.

​
Enable Developer Mode

  1. In ChatGPT, open Settings.
  2. Select the Connectors tab.
  3. Open Advanced settings and toggle on Developer Mode. This unlocks custom connectors.

​
Add the Operata connector

  1. In Connectors, click Create.
  2. Fill in the connector:
    • Name — Operata.
    • MCP server URL — https://mcp.operata.io/mcp.
    • Authentication — set to OAuth.
  3. Confirm that you trust the application, then create the connector.

​
Authorize the connection

ChatGPT redirects you to the Operata sign-in to authorize the connection. Sign in as your Operata user and approve access. ChatGPT returns to the connector, now connected.

​
Select a group

Pick the group you want to query: ask ChatGPT to run list_groups, then switch_group. Your OAuth session can reach every group your account is scoped to. See Groups and regions.

​
Ask ChatGPT a question that uses Operata data

Turn on the Operata connector for the chat, then ask a question that needs Operata data:
Using Operata, what percentage of calls had poor audio quality this month?
ChatGPT calls the right Operata tool — traces_query for an aggregate like this, or knowledge for a concept question — and answers from your account.

​
Result

The Operata connector shows as connected in ChatGPT’s Connectors settings, and a chat with the connector enabled returns a real value from your account. If authorization fails, confirm your Operata role is Admin or User and re-run the OAuth sign-in. See Troubleshooting.