Design a database schema with Claude, Cursor or any MCP assistant
Describe the schema you need to an assistant that supports MCP, and it works in your DesignDB diagram directly: adding tables, columns and relationships, checking the result, and explaining what it did. You see every change on the canvas as it happens.
How it works
- In Claude, Cursor, VS Code or Claude Code, add DesignDB as an MCP server with one address, then sign in and allow it.
- The assistant can list and read your diagrams, create new ones and apply changes to the ones you can edit.
- It can only use DesignDB's own tools: it cannot share a diagram, change a workspace, touch billing or delete anything.
- Before each change the diagram is saved as a named version, so an edit you do not like is one click to undo.
What the assistant is good for
- A first draft from a paragraph: "a booking system with rooms, guests, reservations and payments".
- Reviewing a schema: missing indexes, tables with no key, inconsistent names.
- Mechanical edits across many tables: rename a convention, add audit columns everywhere.
Plans and limits
Assistants are part of Pro AI and Team: 3,000 assistant calls per person per month, with more available as top-ups. Try the editor itself free in your browser first; the assistant connection needs an account on one of those plans.
Schemas to start from
Questions
Which assistants work?
Any that supports MCP over HTTP, including Claude, Claude Code, Cursor and VS Code. You add one address and sign in.
Can the assistant damage my work?
It can edit the diagrams you can edit, but each edit is preceded by a saved version, and it has no access to sharing, workspaces, billing or deletion.
Does my schema leave DesignDB?
DesignDB gives the assistant the diagram you allow it to read; that goes to the assistant you chose, under that assistant's own terms.