MCP server

A database schema MCP server, tool by tool

DB Planner’s MCP server gives an AI agent 51 tools for database design: read a schema, change it, lay out its ER diagram, review a proposal, and keep it in step with code. This page lists every one, and says which only read.

Free plan, no card needed.

The server at a glance

URL
https://api.dbplanner.io/mcp
Transport
Streamable HTTP
Sign-in
OAuth 2.1 with PKCE, in the browser
Scopes
dbplanner:read, dbplanner:write
Tools
51: 19 read, 32 write
Works on
Schema documents and diagrams, never a live database

Connect it

One URL, then a sign-in the first time the agent uses a tool.

  1. 1

    Add the server

    Run one command in Claude Code:

    claude mcp add --transport http db-planner https://api.dbplanner.io/mcp

    or add it to your .mcp.json:

    .mcp.json
    {
      "mcpServers": {
        "db-planner": {
          "type": "http",
          "url": "https://api.dbplanner.io/mcp"
        }
      }
    }
  2. 2

    Approve once in the browser

    Sign in and choose the access you grant. Read and write are separate scopes, enforced on the server.

  3. 3

    Ask it to design

    The agent works with your real tables, not a copy.

Other clients take the same URL: steps for Cursor, Claude, and VS Code.

Read and write are separate, and the server enforces it

Every tool below is marked Read or Write. A read needs the dbplanner:read scope, which every connection has. A write also needs dbplanner:write, which is a switch on the consent screen. Each write tool checks for that scope on the server, so a connection approved as read-only cannot change anything, whatever the agent attempts.

A write marked Asks first is one that overwrites, deletes, or makes something public. The server advertises that as a hint, and clients use it to decide when to stop and confirm with you. Reads carry the opposite hint, which is why a well-behaved client runs them without interrupting.

Whatever the scope, each tool runs as you. It goes through the same permission checks as the app, so an agent sees the organizations and projects your account can, with the role you hold in each, and no more.

Schemas and diagrams

The documents a project is made of: DBML for a database schema, Mermaid for a class diagram or flowchart. Both draw onto the same board.

Schemas and diagrams: MCP tools
ToolAccessWhat it does
list_diagramsReadSummarise what a project contains, by kind, without reading any document text.
list_documentsReadRead a project’s documents in order, each with its content and kind.
list_tablesReadList every table the documents declare, with the document it lives in, its colour, and its column count.
create_documentWriteAdd a schema or a diagram to a project.
update_documentWrite· Asks firstRename a document or replace its text. Each save is a version in its history.
delete_documentWrite· Asks firstRemove a document from a project.
reorder_documentsWrite· Asks firstChange the order of a project’s existing documents.
set_table_colorWrite· Asks firstSet or clear a table’s header colour, which is stored in the DBML.

The board

Where the cards sit and what is drawn around them. The agent can read a layout, change it, and look at the result.

The board: MCP tools
ToolAccessWhat it does
get_boardReadRead the board: card positions, collapsed cards, sticky notes, drawings, pictures, groups, and links.
get_board_imageReadRender the board as a PNG or an SVG, so the agent can see a layout instead of inferring it from coordinates.
list_drawingsReadList the drawings on a board by id, kind, and bounding box.
update_boardWrite· Asks firstMove, collapse, group, or annotate cards. Only the cards named are changed, so a collaborator’s layout is left alone.
drawWriteDraw a freehand stroke or an arrow.
draw_shapeWriteDraw a rectangle, a diamond, or an ellipse, optionally with text in it.
erase_drawingsWrite· Asks firstErase chosen drawings, or all of them.
add_board_imageWritePut a picture on the board.

Review

Comment threads and proposals. An agent can take part in review, and cannot finish one: there is no tool that merges a proposal.

Review: MCP tools
ToolAccessWhat it does
list_commentsReadRead a project’s comment threads and what each is pinned to.
add_commentWriteComment on a table, a column, or the project, or reply to a thread.
list_proposalsReadRead a project’s proposals with the text each changes and its reviews.
propose_changeWritePropose new text for one or more documents without changing them. A person merges it in the app.

GitHub

For a project linked to a repository. Linking itself happens in a browser, because it means installing the GitHub App.

GitHub: MCP tools
ToolAccessWhat it does
get_github_linkReadRead how a project is linked: repository, branch, path, and format.
get_github_sourceReadRead the linked code files (Prisma, EF Core, Rails, Django, or TypeORM) at the head of the branch.
pull_from_githubWrite· Asks firstReplace the linked document with the .dbml file on the linked branch.
push_to_githubWriteCommit the linked document to its .dbml file, directly or as a pull request.
mark_github_syncedWriteRecord which commit the document now reflects, after the agent has rewritten it from code.
open_proposal_pull_requestWriteOpen a proposal as a GitHub pull request, optionally with its migration file.

Organizations and projects

Finding the way around, and the administration an account’s role allows.

Organizations and projects: MCP tools
ToolAccessWhat it does
whoamiReadSay which account the agent is connected as.
list_orgsReadList the organizations the account belongs to.
get_orgReadRead one organization: members, plan, and billing summary.
list_projectsReadList the projects the account can see in an organization, with its role in each.
get_public_profilesReadResolve display names for a set of email addresses.
create_orgWriteCreate a team organization with a first project.
rename_orgWrite· Asks firstRename an organization.
delete_orgWrite· Asks firstDelete an organization and its projects. Owner only.
upsert_org_memberWrite· Asks firstAdd a member to an organization, or change their role.
remove_org_memberWrite· Asks firstRemove a member from an organization.
create_projectWriteCreate a project in an organization.
update_projectWrite· Asks firstRename a project or change its sort order.
delete_projectWrite· Asks firstDelete a project with its documents and board.
upsert_project_memberWrite· Asks firstAdd a member to a project, or change their role.
remove_project_memberWrite· Asks firstRemove a member from a project.

Publishing and sharing

The only tools that reach people outside the account’s organizations. The server’s instructions tell an agent to ask before using the ones that publish.

Publishing and sharing: MCP tools
ToolAccessWhat it does
get_embed_snippetsReadGet the ready-to-paste README badge, README diagram, and iframe for a project.
publish_schema_docsWritePublish a project’s schema as a public documentation page. Creator only.
unpublish_schema_docsWrite· Asks firstTake a project’s public documentation page down.
browse_templatesReadSearch the public template marketplace.
get_templateReadRead one published template: its description, tables, and relationships.
use_templateWriteCopy a template into an organization as a new project.
list_my_listingsReadList the templates the account has published.
publish_listingWrite· Asks firstPublish a project as a free template. Creator only. No tool can set a price.
update_listingWrite· Asks firstEdit a listing’s title, summary, description, category, and tags.
unpublish_listingWrite· Asks firstTake a template off the marketplace and make its project private again.

What there is no tool for

The gaps are deliberate, and they are where the control sits.

  • Merging a proposal. An agent can propose a schema change and read every proposal. Only a person merges one, in the app.
  • Setting a price. Publishing through MCP always makes a free template. Charging for one needs the seller’s own identity and bank details.
  • Linking a GitHub repository. That means installing the GitHub App and proving the installation is yours, which happens in a browser.
  • Running SQL. The server has no database connection. It works on the design. See schema access vs data access.

You can see the agent working

When an agent uses a tool on a project, it appears in that board’s presence list beside the people there, named after the client and marked as acting for you, with the table it is working on highlighted. A teammate watching cards move knows who is moving them.

For how to work with all this, read how to let an AI agent design your database, and for things to ask it, the prompt library.

MCP server questions

What is the DB Planner MCP server?

A hosted Model Context Protocol server at https://api.dbplanner.io/mcp that lets an AI agent read and edit database schemas, their ER diagrams, and the review around them in DB Planner. It has 51 tools, 19 that read and 32 that write. It works on schema designs and never connects to a database.

Is it free to use?

Connecting and reading are part of the free plan, which is every read tool on this page. An agent making edits, which is every write tool, is part of Pro at $5 a month, with a 7-day free trial.

Can I give an agent read-only access?

Yes. Write access is a switch on the consent screen. With it off, every write tool is refused by the server, because each one checks for the write scope itself. It is not a setting the agent is trusted to respect.

Which clients does it work with?

Any MCP client that supports remote HTTP servers with OAuth sign-in, including Claude Code, Claude Desktop, Claude on the web, Cursor, and VS Code. There is nothing to install and no API key.

Is there anything an agent cannot do?

Yes, by design. No tool merges a proposal, so a person always approves a reviewed change. No tool sets a price on a template. Linking a GitHub repository happens in a browser. And nothing reaches a live database, because the server has no connection to one.

Put your schema on the board

Start on the free plan, no card needed. Pro is $5 a month when you outgrow it.

Start designing free