MxCraft
Menu
Tour Sprinter Claude Security Family Access
Build Mendix apps with Claude · keep the work organised

Plan the Mendix work. Let Claude build it.

MxCraft is for building a Mendix app with Claude and keeping that work organised. Weekly sprints, stories with acceptance criteria and a brief for Claude, tests that land on your desk, tokens counted per story and per sprint — and the model imported from MxScout, so every story knows which module it touches. It runs on your machine, has no dependencies, and keeps everything in files you can read.

See the tour Ask for access 0.1 · private beta
0npm dependencies
127.0.0.1only · loopback server
JSONone folder · your data
2 seatsyou and Claude

An agent builds fast.
A chat is not a plan.

Building a Mendix app with Claude works — until you need to know what was agreed, what is done, what still needs a test and what it all cost. MxCraft keeps that in a board instead of a scrollback: stories, sprints, tests and tokens, next to the model they change.

architects solo builders small teams with an agent
Tour

Five tabs and a drawer.

Six screens of a real project. The numbers come from the files; the text in the drawer is what Claude wrote while it worked, and says so.

The Overview screen: the active sprint with one big number, counters, velocity and recent activity.
The screen you show a manager: one number for the sprint, what is waiting for you, velocity, and what Claude and you did last.
The Sprint board: To do, Running, Testing and Done with cards showing who holds them and tokens used.
To do · Running · Testing · Done. Every card says who holds it — you or Claude — and what it cost in tokens so far. Empty columns are drop zones, not blank space.
The story drawer: intent, estimate, acceptance criteria, refinement questions, decisions, model changes, tests and history.
The whole story in one drawer: intent, Claude's estimate with its reasoning, acceptance criteria, refinement questions and answers, decisions with what was rejected, model changes before and after, tests, history.
The Backlog: the team and roles, stories to refine, stories ready, and the next sprint being planned.
Roles at the top: you are Product Owner, Scrum Master and tester, Claude is the developer. Below: what needs refinement, what is ready, and the next sprint with capacity from velocity.
The Tests screen: a filter by result and a table of tests with their stories and sprint.
Tests are tickets of their own, written by Claude from the acceptance criteria, assigned to you. Pass or fail here; Done is yours to give.
The Model screen: modules from MxScout, the documents of one module, and MxCraft notes.
The model imported from MxScout: modules, documents and call counts, with your notes per module and the stories that touch it.
Sprinter · the core

Real Scrum, two seats.

Stories with a brief

Every story carries acceptance criteria, an estimate with its reasoning, and the prompt Claude gets when it picks the story up. Plan a week in one sitting; the sprint runs from there.

Roles that mean something

You are Product Owner, Scrum Master and tester. Claude is the developer: takes stories from To do in order, moves them to Testing, hands you the test — and never marks Done itself.

Tokens, per story and per sprint

Input and output tokens are the only cost you see — on the card, in the drawer, in the sprint header. No currency, no guessing: tokens per point, sprint after sprint.

Model

The app is in the room.

Import from MxScout — one file, every module and documentmodel.json
Notes per module — what Claude should know before it changes anythingnotes
Changes before and after — written into the story that made themdiff
Descriptions, optional — the prose an agent wrote in MxScoutdescriptions.json

MxCraft never edits the Mendix project. It records what Claude changed in Studio Pro, so the story and the model agree.

Claude

Claude is the developer, not the oracle.

MxCraft ships with no AI inside. Claude Code reaches the board through a skill and writes there instead of in the chat: history, criteria, test results, tokens. What you read on the board is what it did.

01 / skill

sprinter

The rules of the board: weekly sprints, stories in order, Testing means a test for you, Done only after it passes. One skill, the same in MxCraft and Tandem.

02 / transport

MCP, or just the files

A local MCP server lets Claude read the sprint and move stories while the page refreshes live. No server? Claude reads and writes the JSON files directly.

03 / the second seat

Tandem

Watch Claude work on the sprint, step by step with tokens, from its own app on the same board. Stop, ask, approve — without scrolling a chat.

Security

Boring on purpose.

The same rules as MxScout: a local server, no dependencies, plain files. Every claim below is one grep away in the source.

How MxScout does it
✓Zero npm dependencies, no build stepnpm ls → empty
✓Server binds to loopback only127.0.0.1:4290
✓No telemetry, no phone-home, no CDN0 outbound
✓Your data is a folder of JSON filesworkspace/
✓Strict content security policy, no inline stylesstyle-src 'self'
✓Test suite you can run yourselfnpm test
✓Claude's access is a skill you can readskills/sprinter
○Private repository for nowask for access
The family

Three tools, one graph.

The same shell, tokens and components in all three, so you never relearn a screen. The logo is the same three dots, each app in its own colour.

reads

MxScout

Reads a Mendix model on your machine and lays it out as documentation people read: processes, modules, flows, pages, risks.

mxscout.seajack.dev
builds

MxCraft

Builds a Mendix app with Claude and keeps that work organised: sprints, stories, tests and tokens on the model MxScout read. This page.

You are here
runs

Tandem

Hands Claude the sprint and shows its work: steps, tokens, questions for you, tests on your desk. The second seat next to Claude Code.

tandem.seajack.dev
Access

Private beta.
Ask, and you get a link.

MxCraft is not public yet: the repository stays private while the board settles on real projects. If you want to run it on your own Mendix app, ask. The link comes with a launcher for Windows, macOS and Linux and the skill for Claude Code; the only thing to have is Node.js 22.

Ask for access See MxScout
Status0.1 · private beta
Runs onyour machine · 127.0.0.1
NeedsNode.js 22 · a browser
Comes withlauncher · skill for Claude Code
Pairs withMxScout · Tandem