Walk through one, end to end.
Written guides for builders: the path from install to production, a setup guide per MCP client, blueprint walkthroughs, and tutorials as they publish. No courses, no video series — the guides you see are the guides that exist.
Every guide names real operations, real roles and real error codes. Where something is still being written, this page says so. Sending this to the person who has to approve it? The
Install. Connect. Build. Promote.
Four pages, in order: from install to an app in production. Looking for the map rather than the walkthrough? Docs indexes every reference by topic.
- 01Get access
Request an invite
CodeMonster is invite only. We meet, scope what you want to build, and set the desktop app up with you — one organization license covers every builder, so there is no seat to request.
Open - 02Connect
Connect the AI you already pay for
Paste the MCP config, restart your client, run whoami. Claude Code is live-tested first.
Open - 03Build
Build from a blueprint
Copy a starter prompt that already works. Watch the agent stage, preview and commit.
Open - 04Promote
Publish it, or promote it
Platform apps publish Current → Testing → Production in one step. Custom frontends promote develop → staging → production, role-gated, with a non-destructive rollback if you need one.
Open
Connect your MCP client.
One guide per client. Live means live-tested; tbd means documented from the MCP spec and waiting on a live test.
Claude Code
Claude Code spawns the CodeMonster MCP server over stdio and builds through named platform operations. Live-tested: the config block, the opening calls in order, and what each error means.
Setup guideClaude Desktop
Claude Desktop reads MCP servers from its config file and spawns them over stdio. This guide follows the MCP spec and Claude Desktop's documented config; it has not been live-tested yet.
Setup guideCursor
Cursor reads MCP servers from mcp.json and can connect over stdio or HTTP+SSE with a bearer header. This guide follows the MCP spec and Cursor's documented config; it has not been live-tested yet.
Setup guideChatGPT
ChatGPT reaches MCP servers over the network through its connector settings, so it uses the HTTP+SSE endpoint. This guide follows the MCP spec; it has not been live-tested yet.
Setup guideAny MCP client
This is the generic HTTP+SSE setup the client guides are built from. The transport and the guardrails are the ones we run; the per-client steps publish as live after we test that client ourselves.
Setup guidePrompts that already work, and what they build.
Each blueprint is a primitives map plus a starter prompt: the objects, forms, workflows, grids and screens the agent assembles, and the operations it calls to do it.
Field service inspection
A work queue on the inspector's phone, photo and signature capture, and a PDF report emailed to the site contact when the inspection is marked complete.
Open blueprintCompliance checklist
Sectioned checklists worked in stages, a reviewer sign-off with a signature, and a change log that records who changed what on every record.
Open blueprintCRM-lite
Accounts, contacts, tasks and whatever the customer calls the thing in the pipeline — deal, engagement, matter — plus a pipeline grid by stage and a workflow that assigns and emails the owner.
Open blueprintApproval workflow
A request form, routing by amount to a manager or a director, email at every step, and a change log that records who approved what and when.
Open blueprintIntake form and survey
A public form that takes submissions without a sign-in, a triage queue for the team behind it, and a change log on every record.
Open blueprintOps dashboard frontend
A Vite/React dashboard over the tables you already have — one object view, one grid, four tiles and a trend — deployed and promoted through dev, staging and production.
Open blueprintNo tutorials yet. Read these instead.
Ask a person.
Builders bring an app in progress; we look at the diff together and answer what the guides did not. Cadence and channel are being set — the community page carries the current state, the code of conduct, and the showcase.
Stuck on a specific call? Write to support. Include the operation you called and the exact error text.
Where builders gather · Every question, one page · The security hub
Bring us something you want built.
CodeMonster is invite only while we work directly with early adopters. Request an invite and we will meet, scope what you want to build, and get you productive. You bring the AI subscription you already pay for.