Connect Cursor

Prerequisites

• The CodeMonster desktop app, signed in with your organization license. It shows the server URL and the token for your session. Desktop builds are being finalized for launch — request access and we send the installer link the day the build for your operating system ships.
• Cursor, signed in on your own plan. That traffic goes to your AI provider under your account and does not route through us.
• A project with a .cursor/mcp.json file (per project) or ~/.cursor/mcp.json (every project).

Configuration

Both values come from the desktop app after sign-in: the server URL and the token. The block below carries a placeholder for each.

{
  "mcpServers": {
    "codemonster": {
      "url": "<server URL shown in the desktop app>",
      "headers": {
        "Authorization": "Bearer <token shown in the desktop app>"
      }
    }
  }
}

Paste the block into mcp.json, replace both placeholders, then open Cursor’s MCP settings and confirm codemonster lists its tools.

That token acts with your permissions on every call, so treat it like a password: it belongs in the config file, never in a prompt, a shared chat or a repository. Cursor also supports stdio; if you prefer that, swap url and headers for the command the desktop app shows.

First calls

Ask Cursor to run these in order. whoami confirms the account; list-tenants and then use-tenant set the tenant context, and no data write goes through without it.

get-domain-knowledge hands the agent the platform’s conventions — build order, object prefixes, groups first, publish to land. list-solutions shows what exists; create-solution starts something new.

Verify it worked

• whoami returns your email and your account. A 401 here means the token is wrong; see below.
• list-tenants returns at least one tenant, and use-tenant echoes the one you chose.
• A data write attempted before use-tenant fails fast with Tenant context required. That failure is the guardrail working.
• .cursor/mcp.json is per project, so a second project opens its own server session — run list-tenants and use-tenant again there.
• After get-domain-knowledge, the agent’s next plan uses the platform’s own vocabulary: objects, forms, screens, groups.

Troubleshooting

• Cursor lists codemonster with a red dot — Cursor could not reach the URL, or the header was rejected. Open the server’s /health URL in a browser: if it answers {"ok":true}, the server is reachable and the problem is the token.
• 401 — the header is missing, the token is expired or revoked, or the Bearer prefix was lost in the paste. The server returns nothing else: no tool list, no schema, no server info. Copy the token again from the desktop app.
• Tenant, transaction and freeze errors — Tenant context required, concurrent_mutation_blocked, staged edits vanishing after 60 idle seconds, and 403 on a solution frozen against AI edits behave the same on every client. Each one, and what to do about it, is documented once on the control surface.

Next

• Build something real: the field-service inspection blueprint is a starter prompt plus the primitives map.
• Read the control surface for every operation family and the transaction lifecycle.
• The full reference is being published on codemonster.dev; /docs tracks its status.