# Other

If your AI tool doesn't have a pre-built Airtable connector, you can still connect it. Any MCP client that supports Streamable HTTP transports can talk to the Airtable MCP server. The server is available to all users on all plans.

## Manual configuration

Follow your AI tool's instructions for connecting to a remote MCP server, and point it at the Airtable MCP server URL:

```
https://mcp.airtable.com/mcp
```

Most clients read a JSON config file with an `mcpServers` block. The Airtable entry looks like this:

```json
{
    "mcpServers": {
        "airtable": {
            "type": "http",
            "url": "https://mcp.airtable.com/mcp"
        }
    }
}
```

The location of the config file and the exact syntax for referencing environment variables vary by client. Check your client's documentation, or the per-client guides in this section, for where the file lives.

## Authentication

By default, clients authenticate with Airtable through an auto-generated OAuth client for each new connection via _Dynamic Client Registration (DCR)_. No extra configuration is required—your client opens a browser OAuth flow where you choose exactly which bases, apps, and workspaces to connect. You can manage those permissions any time from the [third party integrations pane](https://airtable.com/?integrations=thirdParty).

### Static OAuth client

Some organizations want all users to authenticate through a single, allow-listable OAuth client instead of DCR.

1. Register an [OAuth integration](https://airtable.com/create/oauth) using the redirect URI your MCP client requires.
2. Grant it the following scopes:

```
data.records:read
data.records:write
schema.bases:read
schema.bases:write
data.recordComments:read
data.recordComments:write
workspacesAndBases:read
```

3. Enter its OAuth client ID in your client's config file.

### Personal access token (PAT)

PATs are well-suited for CLI, scripts, and server-side setups where you want consistent, predictable access boundaries.

1. [Create a personal access token](/create/tokens/new?scopes=data.records:read,data.records:write,schema.bases:read,schema.bases:write,data.recordComments:read,data.recordComments:write,workspacesAndBases:read) with the Airtable MCP scopes pre-selected (remove any you don't need to limit access).
2. Store your PAT as an environment variable (e.g., `AIRTABLE_PAT`) and pass it as an `Authorization` header:

```json
{
    "mcpServers": {
        "airtable": {
            "type": "http",
            "url": "https://mcp.airtable.com/mcp",
            "headers": {
                "Authorization": "Bearer ${AIRTABLE_PAT}"
            }
        }
    }
}
```