bitable

This MCP server exposes Lark Bitable data via the Model Context Protocol, enabling Claude and other clients to interact with Bitable tables using predefined tools. The available tools let you list the tables, describe a table's schema, and execute read queries against the underlying Bitable data. Specifically, you can:

• list_table: Retrieve a JSON-encoded list of table names for the connected Bitable workspace.
• describe_table: Provide a table name to obtain a JSON-encoded list of its columns and types.
• read_query: Run a SQL-like query to read data from the tables and receive a JSON-encoded result set. To use these tools, ensure your environment is configured with a PERSONAL_BASE_TOKEN and APP_TOKEN, which authenticate your access to Bitable. The server can be run via uvx (as shown in the installation steps) and will expose these tools to your MCP-enabled client. If you prefer Python, you can also run the server with python -m bitable_mcp, which uses the same tool set through the same API surface.

Prerequisites:

• Install uvx in your environment (or use Python with the bitable_mcp module).
• Obtain your PERSONAL_BASE_TOKEN and APP_TOKEN from your Bitable account.

Option A: Using uvx (recommended for Claude CLI integration)

1. Install uvx and start the server:

# Example: run the MCP server with uvx
PERSONAL_BASE_TOKEN=your_personal_base_token APP_TOKEN=your_app_token uv run --with uv --with bitable-mcp bitable-mcp-install

2. Verify the server is running and accessible via MCP tooling.

Option B: Using pip installation (Python)

1. Install the package:

pip install bitable-mcp

2. Run via python -m bitable_mcp:

PERSONAL_BASE_TOKEN=your_personal_base_token APP_TOKEN=your_app_token python -m bitable_mcp

3. Confirm the server is running and the tools are available through your MCP client.

Option C: Configure for Claude or Zed (as shown in the README)

• For Claude via uvx:

"mcpServers": {
  "bitable-mcp": {
    "command": "uvx",
    "args": ["bitable-mcp"],
    "env": {
      "PERSONAL_BASE_TOKEN": "your-personal-base-token",
      "APP_TOKEN": "your-app-token"
    }
  }
}

• For Claude via Python (module):

"mcpServers": {
  "bitable-mcp": {
    "command": "python",
    "args": ["-m", "bitable_mcp"],
    "env": {
      "PERSONAL_BASE_TOKEN": "your-personal-base-token",
      "APP_TOKEN": "your-app-token"
    }
  }
}

Include the same environment variables in your Zed settings if you configure through that client as well.

Tips and common considerations:

• Ensure your PERSONAL_BASE_TOKEN and APP_TOKEN are kept secret and not checked into version control.
• If you switch between uvx and Python, keep the tokens consistent across configurations.
• When troubleshooting, you can use the MCP inspector to debug uvx installations as noted in the README.
• If your environment uses a firewall or proxy, make sure MCP traffic to Bitable APIs is allowed.
• The current tooling supports list_table, describe_table, and read_query; newer tools may be added, so check for updates in the MCP server repository or README for changes.