Setup
Open MCP settings
Go to Cursor Settings > MCP and click Add new global MCP server (or Add new project MCP server for project-scoped config).
Paste the config
your-api-key-here with your OpenCX API key.Project vs Global Config
| Scope | File | Shared with team | Use when |
|---|---|---|---|
| Project | .cursor/mcp.json in repo root | Yes (commit the file) | Team shares the same MCP setup |
| Global | ~/.cursor/mcp.json | No | Personal tools across all projects |
When using project-scoped config, reference
OPENCX_API_KEY as an environment variable in the env block — don’t hardcode the key in a committed file. Each team member sets the key in their local shell profile or .env.Agent Mode vs Ask Mode
Cursor has two chat modes:- Agent mode — can call MCP tools, read/write files, run commands. This is where OpenCX tools work.
- Ask mode — read-only, no tool calls. MCP tools are unavailable.
Debugging
If the server isn’t connecting or tools aren’t appearing:- Check the MCP panel — go to Cursor Settings > MCP. Each server shows a status indicator (green = connected, red = error). Click the server name to see logs.
- Restart the server — click the refresh icon next to the server name in the MCP panel.
- Check the output — Cursor shows MCP tool calls and responses inline in the chat. If a tool call fails, the error message appears in the response.
- Verify Node.js — run
node --versionin Cursor’s terminal. The MCP server requires Node.js 18+.
Related Documentation
Get Started
API key setup and all client configs
VS Code
mcp.json and Copilot Chat
Prompt Library
Ready-to-use prompts by domain
Troubleshooting
Common issues and fixes