DDD Studio is currently in closed alpha. Signing in with Google or GitHub counts as your application to join. Please note that applying does not guarantee access.

Product · Agents

Your agent works where you work.

DDD Studio speaks the Model Context Protocol. Connect Claude or any other MCP client, and it reads and edits your boards and your model with exactly the permissions you have.

Across the whole way

On boards and in the model

The agent does not just execute. It can ask the tool to explain the metamodel, and to explain a modeling decision itself — what an aggregate, a policy or a mapping pattern is for, and when its neighbour is the better shape.

  • Adds, edits and removes cards, areas and connections on a sketch board
  • Reads and helps author domain stories
  • Creates nodes, flows, slices, scenarios and glossary terms
  • Every change appears live in your open canvas

> Turn the workshop board into a first draft of the Lending context.

  • ⏺get_sketch_board · Big Picture
  • ⏺save_version · "before Lending draft"
  • ⏺explain_concept · aggregate vs. policy
  • ⏺create_node · aggregate loan
  • ⏺create_slice · check out a book
  • ⏺add_scenario · no copy left → rejected

“Loan” is its own aggregate: the rule that a copy can only be lent once has to hold in one place. The hotspot from the workshop is now a scenario.

live in your open canvas

An agent session: the agent reads a sketch board, saves a version, asks for an explanation, creates an aggregate and a slice, and adds a scenario.

Built so you can trust it

Same permissions as you

Sign-in uses OAuth against the same login as the app. The agent sees and edits what you can, and nothing else.

A version before every change

Your model or board is backed up automatically before the agent changes it.

Restore stays human

An agent can save a named version before a big restructuring, but cannot restore one.