describe_table
describe_table by table name
LABSCO SUMMARY
Three tools, and they are the three a SQL client needs: discover, describe, query.
list_table and describe_table exist so a query can be written against real table and column names rather than guessed ones, which is the difference between an agent using this successfully and an agent inventing a schema. read_query is read-only by name, so nothing here writes back into the base — anything that changes a record belongs elsewhere. The credential pair is the thing to sort out before setup, since the personal base token and the app token are two different values and both are needed.
What it is
A Bitable client with three tools — list the tables in the current base, describe one of them by name, and run a read query against it in SQL.
What you get
- list_table returns the tables in the current Bitable.
- describe_table returns one table's structure by name.
- read_query runs a SQL read against the base.
Requirements
A Bitable base and two credentials for it: a personal base token in PERSONAL_BASE_TOKEN and the app token in APP_TOKEN.
Setup effort
One command plus a key — uvx bitable-mcp, then supply credentials
USE CASES
01
Answering a question from a Bitable base without exporting it
Discover the table, read its structure, then write the query against real column names rather than assumed ones.
02
Finding out what a base actually contains
The table list and the per-table structure are the whole schema view, which is what an agent needs before it can be useful here.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list_table
list table for current bitable
read_query
read_query by sql
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. All three tools only read: list, describe and a SQL SELECT.
Requires
- uvx on PATH
- PERSONAL_BASE_TOKEN in your environment
- APP_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx bitable-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"bitable-mcp": {
"command": "uvx",
"args": [
"bitable-mcp"
],
"env": {
"PERSONAL_BASE_TOKEN": "<YOUR_PERSONAL_BASE_TOKEN>",
"APP_TOKEN": "<YOUR_APP_TOKEN>"
}
}
}
}Zed
ZED · JSON
{
"context_servers": {
"bitable-mcp": {
"command": "uvx",
"args": [
"bitable-mcp"
],
"env": {
"PERSONAL_BASE_TOKEN": "<YOUR_PERSONAL_BASE_TOKEN>",
"APP_TOKEN": "<YOUR_APP_TOKEN>"
}
}
}
}