Airtable MCP Server

Requirements: Node.js

1. Install Node.js (version 18 or higher) and npm from nodejs.org
2. Verify installation:

   node --version
   npm --version
   

Obtaining an Airtable API Key

1. Log in to your Airtable account at airtable.com
2. Create a personal access token at Airtable's Builder Hub
3. In the Personal access token section select these scopes:
   • data.records:read
   • data.records:write
   • schema.bases:read
   • schema.bases:write
4. Select the workspace or bases you want to give access to the personal access token
5. Keep this key secure - you'll need it for configuration

Installation

Method 1: Using npx (Recommended)

1. Navigate to the Claude configuration directory:
   • Windows:

     C:\Users\NAME\AppData\Roaming\Claude

   • macOS:

     ~/Library/Application Support/Claude/

   You can also find these directories inside the Claude Desktop app: Claude Desktop > Settings > Developer > Edit Config
2. Create or edit

   claude_desktop_config.json

   :

{
  "mcpServers": {
    "airtable": {
      "command": "npx",
      "args": ["@felores/airtable-mcp-server"],
      "env": {
        "AIRTABLE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Method 2: Using mcp-installer:

1. Install mcp-installer
2. Install the Airtable MCP server by prompting Claude Desktop:

Install @felores/airtable-mcp-server set the environment variable AIRTABLE_API_KEY to 'your_api_key'

Method 3: Local Development Installation

# Clone the repository
git clone https://github.com/felores/airtable-mcp.git
cd airtable-mcp

# Install dependencies
npm install

# Build the server
npm run build

# Run locally
node build/index.js

{
  "mcpServers": {
    "airtable": {
      "command": "node",
      "args": ["path/to/airtable-mcp/build/index.js"],
      "env": {
        "AIRTABLE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Verifying Installation

1. Start Claude Desktop
2. The Airtable MCP server should be listed in the "Connected MCP Servers" section
3. Test with a simple command:

List all bases

Features

Available Operations

Base Management

• list_bases

  : List all accessible Airtable bases

• list_tables

  : List all tables in a base

• create_table

  : Create a new table with fields

• update_table

  : Update a table's name or description

Field Management

• create_field

  : Add a new field to a table

• update_field

  : Modify an existing field

Record Operations

• list_records

  : Retrieve records from a table

• create_record

  : Add a new record

• update_record

  : Modify an existing record

• delete_record

  : Remove a record

• search_records

  : Find records matching criteria

• get_record

  : Get a single record by its ID

Field Types

• singleLineText

  : Single line text field

• multilineText

  : Multi-line text area

• email

  : Email address field

• phoneNumber

  : Phone number field

• number

  : Numeric field with optional precision

• currency

  : Money field with currency symbol

• date

  : Date field with format options

• singleSelect

  : Single choice from options

• multiSelect

  : Multiple choices from options

Field Colors

• blueBright

  ,

  redBright

  ,

  greenBright

• yellowBright

  ,

  purpleBright

  ,

  pinkBright

• grayBright

  ,

  cyanBright

  ,

  orangeBright

• blueDark1

  ,

  greenDark1

Contributing

1. Fork the Repository
   • Visit https://github.com/felores/airtable-mcp
   • Click the "Fork" button in the top right
   • Clone your fork locally:

     git clone https://github.com/your-username/airtable-mcp.git
     

2. Create a Feature Branch

   git checkout -b feature/your-feature-name
   

3. Make Your Changes
   • Follow the existing code style
   • Add tests if applicable
   • Update documentation as needed
4. Commit Your Changes

   git add .
   git commit -m "feat: add your feature description"
   

5. Push to Your Fork

   git push origin feature/your-feature-name
   

6. Create a Pull Request
   • Go to your fork on GitHub
   • Click "New Pull Request"
   • Select your feature branch
   • Describe your changes in detail

Development Guidelines

• Use TypeScript for new code
• Follow semantic commit messages
• Update documentation for new features
• Add examples for new functionality
• Test your changes thoroughly

Getting Help

• Open an issue for bugs or feature requests
• Join discussions in existing issues
• Ask questions in pull requests

• Adding new features
• Fixing bugs
• Improving documentation
• Suggesting enhancements

License