The Bitable MCP server provides access to Lark Bitable through the Model Context Protocol, allowing users to interact with Bitable tables using predefined tools. This server enables querying and manipulating Bitable data directly from AI assistants that support MCP.
To quickly install and configure the server for Claude, use the following command:
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_base_token
and your_app_token
with your actual Bitable API tokens.
If you prefer manual installation with uvx, ensure uvx is installed first, then add to your Claude settings:
"mcpServers": {
"bitable-mcp": {
"command": "uvx",
"args": ["bitable-mcp"],
"env": {
"PERSONAL_BASE_TOKEN": "your-personal-base-token",
"APP_TOKEN": "your-app-token"
}
}
}
Alternatively, you can install via pip:
pip install bitable-mcp
Then modify your Claude settings:
"mcpServers": {
"bitable-mcp": {
"command": "python",
"args": ["-m", "bitable_mcp"],
"env": {
"PERSONAL_BASE_TOKEN": "your-personal-base-token",
"APP_TOKEN": "your-app-token"
}
}
}
To use with Zed editor, add to your Zed settings.json:
Using uvx:
"context_servers": [
"bitable-mcp": {
"command": "uvx",
"args": ["bitable-mcp"],
"env": {
"PERSONAL_BASE_TOKEN": "your-personal-base-token",
"APP_TOKEN": "your-app-token"
}
}
],
Using pip:
"context_servers": {
"bitable-mcp": {
"command": "python",
"args": ["-m", "bitable_mcp"],
"env": {
"PERSONAL_BASE_TOKEN": "your-personal-base-token",
"APP_TOKEN": "your-app-token"
}
}
},
The Bitable MCP server provides three main tools:
Lists all tables available in the current Bitable instance.
Describes a specific table by its name.
Executes SQL queries to read data from Bitable tables.
To debug the server with the MCP inspector (for uvx installations):
npx @modelcontextprotocol/inspector uvx bitable-mcp
This helps troubleshoot any connection or configuration issues with your MCP server.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.