Skip to main content
Connect Cursor to the Operata MCP Server so you can ask Operata-data questions from the editor’s chat. Ask for yesterday’s average MOS and Cursor answers from your account. OAuth is the recommended way to connect. Use an API key only for automated, non-interactive integrations. For the difference, roles, and prerequisites, see the MCP overview.

Before you start

Open Cursor’s MCP configuration

Cursor reads MCP servers from a per-project file at .cursor/mcp.json and a global file at ~/.cursor/mcp.json. The project file overrides the global one. Open whichever scope matches how you want to use the server.

Add the Operata MCP server

Connect over OAuth

Add the server to the mcpServers object:
.cursor/mcp.json

Connect with an API key

Use the API key endpoint for automated integrations. The key can only reach the single group it was created in.
.cursor/mcp.json
Replace <your-operata-api-key> with your key.

Reload Cursor

Reload the Cursor window (Command Palette → Developer: Reload Window). Open Cursor’s MCP panel and confirm the operata server shows a green status and lists the Operata tools. On an OAuth connection, a browser window opens on first use to sign in to Operata and authorize the session.

Select a group

On an OAuth session, pick the group you want to query: run list_groups, then switch_group. An API-key session is already fixed to its own group. See Groups and regions.

Ask Cursor a question that uses Operata data

In Cursor’s chat, ask a question that needs Operata data:
Run a query against Operata for the average MOS across all contacts yesterday.
Cursor calls the right Operata tool — traces_query for an aggregate like this — and renders the result inline.

Result

Cursor’s MCP panel lists operata as connected, with the full Operata tool surface. A chat question that needs Operata data invokes a tool and returns a real value from your account. A 401 in the tool-call trace means the credential is wrong or expired; a 403 means a group problem. See Troubleshooting.