Summary
The diagram on screen changes as you describe it.
Because it drives the drawdb tab you already have open, you watch the schema take shape instead of reading a text description of it — and get_issues plus export_sql mean the same session ends with validated DDL. The browser tab is the server's other half; nothing happens while drawdb is closed.
What it is
A bridge between your assistant and a drawdb diagram open in the browser. The command starts a local WebSocket relay, drawdb finds it, and the diagram becomes readable and writable.
What you get
- The full diagram: tables with fields, canvas layout, relationships and target database type
- Tables listed, added, renamed, recoloured and deleted, with fields added, dropped or altered
- Foreign keys added and removed, with cardinality and constraint rules
- Tables repositioned on the canvas
- The target database switched between MySQL, PostgreSQL, SQLite, MariaDB, T-SQL, Oracle and generic
- Validation issues surfaced: duplicate names, missing primary keys, empty tables, type mismatches
- DDL generated for the target database, with columns, constraints and foreign keys
- The diagram cleared, and the last action on the undo stack inspected
- A connection test against the browser session
Requirements
Node.js 18 or newer and npx. drawdb has to be open in your browser — it scans for the relay on startup and shows a green MCP dot in its header once it has found one.
Setup effort
One command — npx mcp-drawdb