db-planner

MCP开发工具

提供方 CNC Software Solutions

开发工具 未标注 OAuth 授权 社区 / 第三方 ClaudeCursorVS CodeCodex

由 CNC Software Solutions 提供的 MCP 服务器,未标注。

一句话选型结论

按资料字段整理

db-planner 属于开发工具类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 6 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量6暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

database schema sql erd postgres mysql sql server diagram

支持客户端

适用场景

databaseschemasql

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 6 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 6 个工具,职责相对集中,接入后不容易误操作。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
db-planner当前 6 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方CNC Software Solutions上游标注的维护方 CNC Software Solutions
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

6.1 KB
来自项目仓库与上游目录的原文,未做删改

DB Planner MCP server

Hosted MCP server for DB Planner that lets any MCP client edit database schemas (DBML/SQL), Mermaid diagrams and board layouts. OAuth sign-in, nothing to install.```
https://api.dbplanner.io/mcp


This repository is documentation. The server is built into the DB Planner API and there is no code to run: add the URL to your client, sign in once in the browser, and your agent has 38 tools over your projects.

## What is DB Planner

DB Planner is a collaborative database design tool. You write schemas in DBML or import SQL dumps (PostgreSQL, MySQL and SQL Server), sketch diagrams in Mermaid, and lay both out on a shared board that renders relationships, notes and drawings in real time. The template marketplace is where published schemas are shared.

## Connect

### Claude Code```bash
claude mcp add --transport http db-planner https://api.dbplanner.io/mcp

Cursor and other clients with a JSON config```json

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


The `url` is the same everywhere; the `type` value is not. Claude Code's `.mcp.json` takes `http` as above, Cursor's `.cursor/mcp.json` needs no `type` at all, and Cline's `mcp.json` takes `streamableHttp`. Check your client's documentation for its remote-server shape.

### Claude.ai and Claude Desktop

Settings, then Connectors, then Add custom connector. Paste the URL. Leave authentication on "Always required" and the OAuth client on "register one automatically". No headers.

### MCP Inspector```bash
npx @modelcontextprotocol/inspector

Click Add Servers, then fill in the form: server ID db-planner, transport streamable-http, URL https://api.dbplanner.io/mcp. Add it, switch it on, and the consent screen opens in the browser.

On every client the first tool call opens the DB Planner consent screen. Sign in, pick the scopes, and you are connected. No password or API key is stored in the client configuration. An agent setting this up on your behalf should read llms-install.md.

Authentication

The endpoint is protected by OAuth 2.1 with PKCE. Discovery is standard, so clients configure themselves from the URL alone:

  • https://api.dbplanner.io/.well-known/openid-configuration
  • https://api.dbplanner.io/.well-known/oauth-protected-resource
  • Dynamic client registration at https://api.dbplanner.io/connect/register, for both public clients (token_endpoint_auth_method=none) and confidential ones (client_secret_post, client_secret_basic)

Two scopes are the whole permission model, and the split is enforced on the server, not in the client:

Scope Grants
dbplanner:read Every read tool. Always granted, because the endpoint requires it.
dbplanner:write The mutating tools, checked per tool. Also covers publishing to the public marketplace.

MCP clients ask for both. Read is always granted, and write is a checkbox on the consent screen, on by default. Turning it off means the token is issued without write even though the client requested it, so a read-only connection is a real guarantee rather than a client-side courtesy.

Clients also request offline_access. That is a session mechanism rather than a permission: it yields a refresh token so the connection survives token expiry, and it is granted whenever asked.

A tool never sees more than the signed-in user can see in the app: organization and project roles are resolved from the token's subject and enforced by the same services the web app uses.

Tools

Every tool carries a title, a read-only or destructive hint, an openWorldHint of false, a description on every parameter and an output schema, so clients can run reads without confirmation prompts and read structured results instead of parsing text.

Group Read Write
Session whoami, get_public_profiles
Organizations list_orgs, get_org create_org, rename_org, delete_org, upsert_org_member, remove_org_member
Projects list_projects create_project, update_project, delete_project, upsert_project_member, remove_project_member
Documents list_documents, list_diagrams create_document, update_document, delete_document, reorder_documents, set_table_color
Board get_board, get_board_image, list_tables, list_drawings update_board, draw, draw_shape, erase_drawings, add_board_image
Marketplace browse_templates, get_template, list_my_listings use_template, publish_listing, update_listing, unpublish_listing

A few things worth knowing before an agent calls them:

  • Design lives in documents, never on the board. Tables, columns, references, enums, classes and flowchart steps are derived by parsing a document, so the design changes through create_document and update_document and the board follows. There is no tool that creates a table directly.
  • get_board_image renders the board to a PNG so the model can look at a layout rather than infer it from coordinates. Pass format='svg' for the vector source as text.
  • draw and draw_shape are the drawing tools. Ink and arrows are one tool with a kind; rectangles, diamonds and ellipses, with optional bound text, are the other. Both mint ids and round coordinates the way the app does. Free text on its own, groups and links go through update_board.
  • update_board takes a partial delta. Send only the card ids you are changing; a null value deletes one. It is the same merge contract the app uses, so an agent moving one card does not clobber a collaborator's layout.
  • Publishing is creator-only, and no tool takes a price. Only the person who created a project may list it, and a listing published through MCP is always free. Pricing requires Stripe onboarding that nobody can do on someone's behalf.

Where it is listed

  • Official MCP Registry as io.dbplanner/db-planner
  • Smithery
  • Glama
  • mcp.so
  • cursor.directory

Support

Questions and problems: support@dbplanner.io. Product documentation is at dbplanner.io/features.

License

This documentation is released under the MIT License. DB Planner itself is a hosted product; see dbplanner.io/pricing.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
db-planner 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

db-planner 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

db-planner 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

db-planner 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

db-planner 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

db-planner 能提供哪些能力?

资料显示约 6 个工具;能力标签包括 database、schema、sql、erd、postgres、mysql。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。