This MCP server provides access to Lark Bitable through the Model Context Protocol. It allows users to interact with Bitable tables using predefined
Bitable MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. This MCP server provides access to Lark Bitable through the Model Context Protocol. It allows users to interact with Bitable tables using predefined tools.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Bitable MCP is connected, these are the calls the assistant has available:
list_table — List tables for the current BitableReturns — A JSON-encoded list of table namesdescribe_table — Describe a table by its nameParameters — - name (str): The name of the table to describeread_query — Execute a SQL query to read data from the tablesClaude — To install and configure the server, use the following command: bash PERSONAL_BASE_TOKEN=your_personal_base_token APP_TOKEN=your_app_token uv runCursor — The Cursor tool exposed by this serverWindsurf — The Windsurf tool exposed by this serverYou will need 2 environment variables: PERSONAL_BASE_TOKEN, APP_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Bitable MCP's toolset — list_table, Returns, describe_table and 5 more — is a fair guide to whether it matches your workflow. It is maintained by lloydzhou; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Bitable MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_table | List tables for the current Bitable. |
| Returns | A JSON-encoded list of table names. |
| describe_table | Describe a table by its name. |
| Parameters | - name (str): The name of the table to describe. |
| read_query | Execute a SQL query to read data from the tables. |
| Claude | To install and configure the server, use the following command: bash PERSONAL_BASE_TOKEN=your_personal_base_token APP_TOKEN=your_app_token uv run --with uv --with bitable-mcp bitable-mcp-install Replace your_personal_bas |
| Cursor | The Cursor tool exposed by this server. |
| Windsurf | The Windsurf tool exposed by this server. |
2) Modify your Claude settings
```json
"mcpServers": {
"bitable-mcp": {
"command": "python",
"args": ["-m", "bitable_mcp"],
"env": {
"PERSONAL_BASE_TOKEN": "your-personal-base-token",
"APP_TOKEN": "your-app-token"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PERSONAL_BASE_TOKEN | Credential the server authenticates with. | Yes |
| APP_TOKEN | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.