Model Context Protocol moderate risk

Airtable

Airtable MCP server enables LLMs to read, write, and manage Airtable databases, providing access to data and schema via API key authentication.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwriteadmin

Quickstart

Config

{
  "mcpServers": {
    "airtable": {
      "command": "npx",
      "args": [
        "-y",
        "airtable-mcp-server"
      ],
      "env": {
        "AIRTABLE_API_KEY": "pat123.abc123",
      }
    }
  }
}

Exposed MCP Tools (15)

safe

list_records

Lists records from a specified Airtable table.

Read-only operation.

safe

search_records

Searches for records containing specific text.

Read-only operation.

safe

list_bases

Lists all accessible Airtable bases.

Read-only operation.

safe

list_tables

Lists all tables in a specific base.

Read-only operation.

safe

describe_table

Gets detailed information about a specific table.

Read-only operation.

safe

get_record

Gets a specific record by ID.

Read-only operation.

moderate

create_record

Creates a new record in a table.

Creates new data.

high

update_records

Updates one or more records in a table.

Modifies existing data.

critical

delete_records

Deletes one or more records from a table.

Destructive operation.

high

create_table

Creates a new table in a base.

Modifies the database schema.

high

update_table

Updates a table's name or description.

Modifies the database schema.

high

create_field

Creates a new field in a table.

Modifies the database schema.

high

update_field

Updates a field's name or description.

Modifies the database schema.

moderate

create_comment

Creates a comment on a record.

Adds new data.

safe

list_comments

Lists comments on a record.

Read-only operation.

Safety Assessment

This server offers significant utility but requires careful API key management. Limiting scopes and deploying behind a reverse proxy are crucial for mitigating risks. The HTTP transport option should only be used in secured environments.

API key authentication required
Granular scopes can limit access
No direct code execution
Can be deployed behind a reverse proxy

API key compromise grants full access within scopes
Potential for data modification or deletion
No built-in rate limiting
HTTP transport lacks built-in authentication