Connect Claude Code

Prerequisites

• The CodeMonster desktop app, signed in with your organization license. It runs the local MCP server and shows the exact command Claude Code 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 Code, signed in on your own Claude plan. That traffic goes to your AI provider under your account and does not route through us.
• A project folder to hold the configuration. Claude Code reads .mcp.json from the project root.

Configuration

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

Save the block above as .mcp.json in your project root and replace the command placeholder with the local server command the desktop app shows after sign-in. Nothing else in the block changes. Start a new Claude Code session and confirm codemonster appears in its list of MCP servers.

Claude Code spawns the server over stdio, so this form carries no URL and no token — the desktop app holds your session, and signing out there ends it.

First calls

Ask Claude Code to run these in order. whoami confirms which account the session belongs to; 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.
• After get-domain-knowledge, the agent’s next plan names objects, forms, screens and groups in the platform’s own vocabulary.

Troubleshooting

• codemonster is missing from the server list — Claude Code reads .mcp.json from the project root when the session starts. Check the JSON is valid, then start a new session from that folder.
• 401 on the first call — the session is not valid: the 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 desktop app and start a new Claude Code session.
• 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.