Connect Claude Desktop

Prerequisites

• The CodeMonster desktop app, signed in with your organization license. It runs the local MCP server and shows the exact command Claude Desktop will spawn. Desktop builds are being finalized for launch — request access and we send the installer link the day the build for your operating system ships.
• Claude Desktop, signed in on your own Claude plan. That traffic goes to your AI provider under your account and does not route through us.
• Access to Claude Desktop’s configuration file, claude_desktop_config.json. Claude Desktop opens it from its developer settings.

Configuration

{
  "mcpServers": {
    "codemonster": {
      "command": "<local MCP server command shown in the desktop app>",
      "args": []
    }
  }
}

Paste the block above into claude_desktop_config.json and replace the command placeholder with the local server command the CodeMonster desktop app shows after sign-in. If the file already has an mcpServers object, add the codemonster entry inside it rather than replacing the object. Quit and reopen Claude Desktop; the server appears in its tools menu once it has started.

First calls

Ask Claude 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 session is not valid; 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.
• Tenant context belongs to the MCP session, and Claude Desktop starts that session when the app launches — set the tenant once per run, and again after a restart.
• After get-domain-knowledge, the agent’s next plan uses the platform’s own vocabulary: objects, forms, screens, groups.

Troubleshooting

• The server never appears — Claude Desktop reads the config only on launch. Check the JSON is valid (a trailing comma is the usual culprit), then quit and reopen the app.
• 401 on the first call — the session is not valid: the CodeMonster desktop app is signed out, or the spawn command is stale. The server returns nothing else — no tool list, no schema, no server info. Sign in again in the CodeMonster desktop app and restart Claude Desktop.
• 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.