Airtable MCP setup: bases, OAuth and records
Choose one base and a few fields. Verify the first connection against a known record.
Prepare a small test table in a selected Airtable base. Record the table name, a known record identifier and two expected field values. This gives you a reference for checking whether the request reaches the right base and returns the intended fields. A similarly named table in another base is not sufficient for this comparison.
Choose the base and sign-in method
Airtable documents https://mcp.airtable.com/mcp as its remote MCP endpoint. OAuth authorisation lets you select bases, apps and workspaces. For a first test, select only the intended scope. The server respects the signed-in person’s Airtable permissions. Your organisation may additionally require an administrator to approve the integration.
Add the HTTP connection in VS Code
Run “MCP: Add Server”, select HTTP and enter the endpoint. The example below uses the VS Code format for .vscode/mcp.json. It contains no credentials: start the connection and complete the browser OAuth flow. Check the account and selected bases in that dialog before authorising the connection.
{
"servers": {
"airtable": {
"type": "http",
"url": "https://mcp.airtable.com/mcp"
}
}
}
Airtable supports dynamic client registration. Some organisations instead use an OAuth app registered and approved in advance. Check that option with your administrator if sign-in is blocked. The VS Code guide explains startup and other configuration formats; use the access planner to record the intended scope.
Run a small read test
Inspect the available tools. First verify that the selected base appears among the accessible bases.
Request the table structure and compare table name, field names and field types with your prepared test table.
Read the known record using a suitable read operation. Limit the request to the required fields and a small result set.
Compare identifier and field values with the Airtable interface. Record the time and selection so another person can repeat the test.
Separate permissions, selection and data
| Observation | Next check |
|---|---|
| Base is missing | Check OAuth authorisation and the signed-in account’s Airtable access. |
| Table exists but the record is absent | Compare table identifier, search filters and the record identifier. |
| Only an interface is shared | Inspect the read operations available for that interface; do not assume full base access. |
| Integration is blocked | Check your organisation’s approval of third-party integrations. |
Do not change fields or records during this first trial. A read request does not remove write permissions from the account. Airtable also supports personal access tokens whose permissions and resources can be restricted explicitly. Treat that path as a separate setup. After changing authorisation, repeat the known-record check. The Airtable registry search shows further provider declarations; a similarly named server may use different connection methods or tools.
- Can I share other bases later?
- Manage the connection in Airtable’s third-party integrations. After a change, check that exactly the intended bases are accessible and that the known read test still returns the expected result.
- Does a successful sign-in verify data access?
- No. Reading a known record establishes whether the intended base, table and fields are accessible. Compare the returned values against the interface.
- Can MCP access more than my Airtable account?
- Documented access follows your account’s permissions. The connection does not override missing base or interface permissions; inspect the authorisation and account role together.
- What does an empty response mean?
- It can result from an unsuitable filter, the wrong table or limited access. Start with a known record identifier and change only one part of the selection at a time.
Find more file and data connections in the app directory.
Vendor documentation checked on 2 October 2026. The checks are a suggested procedure for your environment, not an authenticated account test.
- Airtable: MCP overview
Show retrieval command
curl -s https://airtable.com/developers/agents/mcp/getting-started - Airtable: other clients
Show retrieval command
curl -s https://airtable.com/developers/agents/mcp/other - Airtable: tools reference
Show retrieval command
curl -s https://airtable.com/developers/agents/mcp/tools - VS Code: MCP configuration
Show retrieval command
curl -s https://code.visualstudio.com/docs/agent-customization/mcp-servers