Aitable MCP Server

🚀 AITable MCP Server

A Model Context Protocol server that offers read and write access to AITable.ai. This server empowers LLMs to perform operations like listing spaces, searching nodes, listing records, creating records, and uploading attachments on AITable.ai.

✨ Features

Tools

Environment Variables

• AITABLE_API_KEY: Your AITable personal access token.
• AITABLE_BASE_URL: The base URL of the AITable API. Defaults to https://aitable.ai/fusion. You can set it to {YOUR_CUSTOM_BASE_URL} if you are using the APITable (the open - source version of AITable).

💻 Usage Examples

Basic Usage

You can use this server in MCP clients such as Claude Desktop, CherryStudio, etc.

Claude Desktop

In the case of Claude Desktop, you need to add the following configuration information to the "mcpServers" section of the claude_desktop_config.json file:

For Linux, MacOS:

{
  "mcpServers": {
    "aitable": {
      "command": "npx",
      "args": [
        "-y",
        "/ABSOLUTE/PATH/TO/PARENT/FOLDER/aitable-mcp-server"
      ],
      "env": {
        "AITABLE_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

For Windows:

{
  "mcpServers": {
    "aitable": {
      "command": "npx",
      "args": [
        "-y",
        "D:\\ABSOLUTE\\PATH\\TO\\PARENT\\FOLDER\\aitable-mcp-server"
      ],
      "env": {
        "AITABLE_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with your AITable personal access token and /ABSOLUTE/PATH/TO/PARENT/FOLDER/aitable-mcp-server with the absolute path to the parent folder of this repository.

CherryStudio

If you are using the CherryStudio as an MCP client and a Windows system, your configuration should look like this:

{
  "mcpServers": {
    "aitable": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "D:\\ABSOLUTE\\PATH\\TO\\PARENT\\FOLDER\\aitable-mcp-server"
      ],
      "env": {
        "AITABLE_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Advanced Usage

The MCP inspector is a developer tool for testing and debugging MCP servers.

To inspect an MCP server implementation, there's no need to clone the MCP inspector repo. Instead, use npx. For example, AITable MCP server is built at dist/index.js. Arguments are passed directly to your server, while environment variables can be set using the -e flag:

npx @modelcontextprotocol/inspector -e AITABLE_API_KEY={YOUR_API_KEY} node build/index.js

The other way is to clone the MCP inspector repo and connect the AITable MCP server in the inspector interface.

cd path/to/inspector/
npm start -- -e AITABLE_API_KEY={YOUR_API_KEY}