mcpField
B
Bitable MCP Server

Bitable MCP Server

Local
github.com/lloydzhouProductivity2Updated 8w ago
Repository

About Bitable MCP Server

Bitable MCP Server connects MCP clients to Lark Bitable tables. It provides tools to list and inspect tables and run read-only SQL queries, using the required Bitable tokens for access.

Key features

  1. 01List Bitable tables
  2. 02Inspect table columns
  3. 03Run read-only SQL queries

Use cases

  1. 01Check which tables a Bitable contains
  2. 02Review a table’s column structure
  3. 03Retrieve records with a SQL query

MCP support

It exposes predefined tools to MCP clients for listing tables, describing columns, and querying table data.

#mcp#bitable#mcp-server

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "bitable": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli"
      ]
    }
  }
}
Run commandnpx -y @smithery/cli

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@smithery/cli

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

MseeP.ai Security Assessment Badge

Bitable MCP Server

LightNow capabilities

This MCP server provides access to Lark Bitable through the Model Context Protocol. It allows users to interact with Bitable tables using predefined tools.

Bitable Server MCP server

One click installation & Configuration

Installing via Smithery

To install Bitable Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @lloydzhou/bitable-mcp --client claude
Claude

To install and configure the server, 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 tokens.

Cursor

Coming soon

Windsurf

Coming soon

Available Tools

  • 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.
    • Returns: A JSON-encoded list of columns in the table.

  • read_query - Execute a SQL query to read data from the tables.

    • Parameters:
      • sql (str): The SQL query to execute.
    • Returns: A JSON-encoded list of query results.

Manual installation and configuration

Please make sure uvx is installed before installation.

Add to your Claude settings:

  1. Using uvx
"mcpServers": {
  "bitable-mcp": {
    "command": "uvx",
    "args": ["bitable-mcp"],
    "env": {
        "PERSONAL_BASE_TOKEN": "your-personal-base-token",
        "APP_TOKEN": "your-app-token"
    }
  }
}
  1. Using pip installation
  1. Install bitable-mcp via pip:
pip install bitable-mcp
  1. 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"
    }
  }
}
Configure for Zed

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 installation

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

Debugging

You can use the MCP inspector to debug the server. For uvx installations:

npx @modelcontextprotocol/inspector uvx bitable-mcp

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.