Skip to main content
Connect Cursor to the Operata MCP Server (Model Context Protocol) so you can ask Operata-data questions from inside the editor’s chat.

​
Before you start

  • An Operata account with admin permissions to mint API tokens.
  • An Operata API token scoped to the account you want Cursor to query. See Authentication.
  • Cursor installed and signed in. For Cursor’s general MCP support, see docs.cursor.com.

​
Steps

​
1. Mint an MCP-dedicated API token

Sign in to the Operata console, open Settings → Config → API, and create a new token. Name it MCP — Cursor so you can revoke it independently of other tokens. Copy the value; the console does not show it again.

​
2. 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.

​
3. Add the Operata MCP server

Add the server to the mcpServers object:
Replace $OPERATA_API_TOKEN with the token from step 1.

​
4. 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 (get_schema, traces_list, traces_query, traces_get, traces_span_insights, traces_span_logs, and knowledge).

​
5. Ask Cursor a question that uses Operata data

In Cursor’s chat, ask a question that requires Operata data:
Run a query against Operata for the average MOS across all contacts yesterday.
Cursor calls the appropriate Operata MCP 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 requires Operata data invokes one of the tools and the response contains a real value from your account. A 401 in the tool-call trace means the API token is wrong or revoked. For what each tool does, see Operata MCP server tools.