Tabellum

dev.dudko由 dudko.dev 发布v0.1.2更新于 Oct 25, 2026

MCP bridge to the Tabellum database client: schema, reads, SQL drafts; writes approved in the app.

发布方自己的服务：PDF to Markdown

已验证STDIO仅桌面数据库开发者工具

服务详情

标识符: dev.dudko/tabellum
传输: STDIO
运行时: Desktop only
信任: Verified
发布于: Sep 26, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 dudko.dev。它以软件包形式运行，而不是托管端点，因此没有可与该域名比对的端点。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.dudko%2Ftabellum.svg)](https://sourceweft.com/mcp/dev.dudko%2Ftabellum?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

将 AI 助手连接到 Tabellum 桌面数据库客户端，可查看结构、执行只读查询、起草 SQL，写操作需在应用内确认。

可以做什么: 查看连接、模式、对象、用户与角色，以及按连接开启共享后的样本行
执行只读查询并查看执行计划，打开查询标签页并写入 SQL 草稿
提交写入、DDL 与管理语句，等待你在应用中点击批准
将模式与另一连接或已保存快照对比，并生成补齐差异的迁移语句
列出、读取并提交仪表板与模式设计
适用场景: 适合已在 Tabellum 桌面客户端中管理 PostgreSQL、MySQL/MariaDB、SQL Server 或 BigQuery 的用户，希望助手协助探索结构、起草查询和迁移建议，同时由自己掌控所有改动数据的操作。
运行要求: 需在 macOS、Windows 或 Linux 上安装并运行 Tabellum 桌面应用；npm 包需 Node.js 24 及以上，通过 npx 启动。转发程序会从用户主目录下的配置文件读取应用本地端口和每次安装生成的令牌，无需手动设置密钥。

安装前请注意

助手可读取结构信息、用户与角色，以及在按连接开启行共享时读取样本行。写入、DDL 与管理语句仅作为提案，需在应用中批准，10 分钟后超时失效。调用会在应用的代理日志中留痕；重新生成令牌后需重启 MCP 服务器。

安装

在 SourceWeft 中

打开控制台中的 Tabellum，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照仓库中的启动说明。

README

Tabellum — MCP setup

Let your AI assistant work with your databases through Tabellum, a desktop database client for PostgreSQL, MySQL/MariaDB, SQL Server and BigQuery. The MCP server is hosted by the running app on your machine; this package is a small stdio shim that forwards to it. Queries the assistant writes appear live in the editor, and nothing that changes data runs without your click in the app.

Server: tabellum
Transport: stdio (local process)
Package: @dudko.dev/tabellum-mcp — Node.js 24+
Auth: a per-install token the app generates; the shim reads it for you from ~/.tabellum/mcp.json.

What you can do

With the Tabellum app open, the assistant gets the same tools as the app's own agent — the app serves them, so the list follows the app version. Reads run at once; anything that writes waits for your click in the app.

Tool	What it does
Look around
`list_connections`	Connection names, drivers, read-only flags. No hosts, no users.
`describe_schema`	Every schema of a connection with its table, view, function, procedure and sequence names.
`describe_object`	Columns, indexes, constraints and the `CREATE` of one object.
`list_users`	Users and roles with their flags, where the database lists them.
`sample_rows`	Up to N rows of a table — only where the connection shares rows.
Query
`run_read`	Runs a statement only if the engine classifies it as a read; anything else answers `needs_approval`.
`explain`	The estimated plan of a read; nothing runs.
`propose_write`	A write, DDL or admin statement for your approval in the app (10-minute timeout).
`open_editor_tab`	Open a query tab bound to a connection.
`draft_to_editor`	Type SQL into a tab while you watch, without running it.
Compare schemas
`compare_schemas`	Diff a connection against another or a saved snapshot; with `migration: true`, the statements that close the gap. Nothing runs.
`save_schema_snapshot` / `list_schema_snapshots`	Save a connection's schema to the workspace; list the snapshots.
Dashboards
`list_dashboards` / `get_dashboard`	The workspace's dashboards; one dashboard's file and panels.
`propose_dashboard`	A new or changed dashboard — you see the diff and apply it.
Schema designs
`list_designs` / `get_design`	The workspace's schema designs; one design's file and objects.
`propose_design`	A new or changed design — you see what is added, changed and removed. Nothing runs against a database.
`describe_feature`	The file format and rules of `designer`, `dashboards` or `schema_compare`, read before proposing one.

Resources, for clients that prefer them: tabellum://connections, tabellum://schema/<connection>, tabellum://snapshots, tabellum://dashboards, tabellum://designs. Every call is attributed in the app — a badge on the tab and a line in the agent log.

Install in Claude Code (plugin)

/plugin marketplace add dudko-dev/tabellum-mcp-setup/plugin install tabellum@tabellum/reload-plugins

/plugin marketplace add dudko-dev/tabellum-mcp-setup/plugin install tabellum@tabellum/reload-plugins

Start the Tabellum app first (macOS, Windows or Linux). The shim reads the app's local port and token from ~/.tabellum/mcp.json, written while the app runs; with the app closed every call answers "Tabellum is not running".

Prefer not to use the marketplace? Add the server directly:
claude mcp add tabellum -- npx -y @dudko.dev/tabellum-mcp
claude mcp add tabellum -- npx -y @dudko.dev/tabellum-mcp

Connect from other clients

Claude Desktop

claude_desktop_config.json (Settings → Developer → Edit Config):

json

{  "mcpServers": {    "tabellum": {      "command": "npx",      "args": [        "-y",        "@dudko.dev/tabellum-mcp"      ]    }  }}

{  "mcpServers": {    "tabellum": {      "command": "npx",      "args": [        "-y",        "@dudko.dev/tabellum-mcp"      ]    }  }}

Cursor

~/.cursor/mcp.json or .cursor/mcp.json:

json

{  "mcpServers": {    "tabellum": {      "command": "npx",      "args": [        "-y",        "@dudko.dev/tabellum-mcp"      ]    }  }}

{  "mcpServers": {    "tabellum": {      "command": "npx",      "args": [        "-y",        "@dudko.dev/tabellum-mcp"      ]    }  }}

VS Code (GitHub Copilot / MCP) and other clients

json

{  "servers": {    "tabellum": {      "type": "stdio",      "command": "npx",      "args": [        "-y",        "@dudko.dev/tabellum-mcp"      ]    }  }}

{  "servers": {    "tabellum": {      "type": "stdio",      "command": "npx",      "args": [        "-y",        "@dudko.dev/tabellum-mcp"      ]    }  }}

Safety

The engine classifies, you approve. Every statement is classified by the app's parser; anything that is not a read goes through propose_write and waits for your click. A label claimed by the model never overrides it.
Loopback only. The app listens on 127.0.0.1 with a per-install bearer token (Settings → Agents shows it and can regenerate it).
Row data is opt-in per connection. sample_rows returns rows only where you enabled sharing for that connection.

Troubleshooting

"Tabellum is not running" — open the app, then retry.
Unauthorized after regenerating the token — restart the MCP server in your client so the shim re-reads ~/.tabellum/mcp.json.
A write seems stuck — it is waiting for approval in the app; after 10 minutes it returns declined: timeout.