Connect Cursor
How do I connect Cursor?
Cursor connects to the ZopNight MCP server through `~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` to scope it to one. Cursor reloads the config automatically and lists the server on its Customize page. Reads work at once; writes require an org admin to enable them.
| Setting | Value |
|---|---|
| Config location | ~/.cursor/mcp.json |
| Auth | Personal Access Token (Bearer) |
Paste the config and let Cursor pick it up
Create ~/.cursor/mcp.json to register the server in every project, or .cursor/mcp.json inside one project to scope it there. Paste the configuration below and save. Cursor picks it up automatically and lists it on the Customize page.
The mcp.json block, keyed on url
{ "mcpServers": { "zopnight": { "url": "MCP_SERVER_URL", "headers": { "Authorization": "Bearer MCP_PAT" } } }}Swap MCP_SERVER_URL for the Server URL on your Organisation Settings page, and MCP_PAT for your personal access token (it starts zn_pat_).
Global or per-project
~/.cursor/mcp.json registers the server everywhere. .cursor/mcp.json inside a repo scopes it
to that project, worth doing when a repo maps to one team, so the assistant’s cost questions
land against the right budget.
Cursor picks up changes without a restart; if the server does not appear, check the Customize page rather than reloading the window.
What Cursor can answer at read-only
At the default org setting, read-only, 85 of the 119 tools work immediately. That covers cost totals by team or tag, spend trends, budget health, detected anomalies, the full resource inventory, recommendations with their savings, Kubernetes logs and events, and deploy history.
Ask for a cost overview first; it is the entry point the tool set is designed around.
Unlocking mutating tools for Cursor
Mutating tools sit behind an org-level dial with four positions, each cumulative:
| Tier | What it unlocks |
|---|---|
| Read-only | nothing mutating (the default) |
| Metadata | budgets, recommendation status, smart-tag decisions |
| Reversible | schedules, overrides, tagging policies, deploys and rollbacks |
| Irreversible | start/stop, provisioning, Kubernetes writes, deletes |
Your own RBAC still applies on top: the tier is a ceiling, not a bypass. Roles, user management, credentials and cloud-account deletion are never reachable at any tier.
Cursor connects but no tools appear
Two causes account for almost every case. Either MCP is not enabled for the organisation, or the transport is wrong. MCP is off by default, and an admin turns it on in Organisation Settings. Every mutating call is audit-logged with its source, so MCP activity stays distinguishable from UI and API activity afterwards.
Cursor: troubleshooting
Where is Cursor's mcp.json?
~/.cursor/mcp.json registers the server for every project. A .cursor/mcp.json inside a repo scopes it to that project, which is worth doing when a repo maps to one team so cost questions land against the right budget.
Do I need to restart Cursor after editing mcp.json?
No, Cursor picks up changes on its own. If the server still does not appear, check the Customize page rather than reloading the window.
Does Cursor expect url or serverUrl?
url. Windsurf and Antigravity use serverUrl, so a config copied between them silently fails to register.