Connect Airtable to Claude. For your whole team.
Airtable's official MCP server mirrors the signed-in person's permissions, and its token setup asks for write scopes on records and schema. Loopthink holds one read-only token pinned to the bases you choose, gives every Claude user in your team their own login, and lets Operations, Sales and Management read exactly the tables their role allows.
Free for your own server · Team from €99 · EU-hosted
Airtable in a chat client, today.
Today a team that wants Airtable in an AI client either buys a collaborator seat per person or has one person create a token and share it. Airtable seats are per user, so the token gets shared. A shared token means one person's access for everyone, write scopes because the setup guide asked for them, and email columns going to the model untouched.
One matrix for Airtable. Roles across, tools down.
| Tool | Operations | Sales | Management |
|---|---|---|---|
| Bases & schema | Operations may use Bases & schema | Sales may not use Bases & schema | Management may use Bases & schema |
| Records | Operations may use Records | Sales may use Records | Management may use Records |
| Filtered lists | Operations may use Filtered lists | Sales may use Filtered lists | Management may not use Filtered lists |
| Comments | Operations may use Comments | Sales may not use Comments | Management may not use Comments |
| Write actions off by default | Operations may not use Write actions | Sales may not use Write actions | Management may not use Write actions |
Masked for every role: email and phone columns, collaborator names, attachment URLs.
You set this once. Every Claude user in your team gets exactly this.
Once on the Airtable side, once in Claude.
On the Airtable side
Personal access token, read scopes only, limited to chosen bases
- 1
Airtable → Builder Hub → Personal access tokens (airtable.com/create/tokens) → Create token.
- 2
Add the scopes data.records:read, schema.bases:read and data.recordComments:read. Under Access, add the bases your team should reach, not all resources.
- 3
Paste the token into Loopthink. The token never appears in anyone's client.
In Claude
Custom connector, OAuth
- 1
An Owner opens Organization settings → Connectors → Add and pastes your Loopthink connector URL. On Free, Pro and Max: Customize → Connectors → + → Add custom connector.
- 2
Each team member opens Customize → Connectors, clicks Connect on Loopthink and signs in once with their own account.
- 3
In a chat, the + menu lists the connector. Toggle it on, ask away. No key, no config file.
Custom connectors are available on Free, Pro, Max, Team and Enterprise. On Team and Enterprise only Owners can add one; every member still connects individually, which is exactly what gives each call its own identity.
Steps checked against the vendor documentation on 17 September 2026: Airtable MCP server · Creating personal access tokens · API scopes · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities
Loopthink sits in between: it holds the key, shows Claude a normal login, and applies your roles on every call.
Four checks between Claude and Airtable.
- 01
Identify
OIDC/SSO against your own IdP, including Microsoft Entra. The call runs as the person who made it, never as a shared service account.
- 02
Authorize
Per-role, per-tool, read or write. Anything not explicitly granted never shows up in the tool list in the first place.
- 03
Mask
Field-level masking and pseudonymization applied on your side, before the result travels. The model never sees the raw field. Composio, AnythingMCP and both provider tunnels have no field-level masking at all.
- 04
Log
Who asked, which tool, which records, which fields were masked. One audit trail across every AI client, exportable for review.
What people actually ask Claude about Airtable.
- Operations
“Which onboarding tasks in the Clients base are overdue, and who owns them?”
- Sales
“Show me every deal in stage Proposal, sorted by value.”
- Management
“How many records were added to Leads this month versus last month?”
Each question runs as the person who asked it, with that person's role. A Sales colleague asking the Operations question gets the tools their own role allows, not an error, not more.
Four ways to put Airtable into Claude.
| Native Airtable connector | Build it yourself | Enterprise gateways1 | Loopthink | |
|---|---|---|---|---|
| Per-user identity | One personal login, all its rights | Only if you build it | Yes | Yes, every call runs as the person who asked |
| Tool-level roles | No | Your code | Yes | Yes, write off by default |
| Field masking | No | Your code | Not documented | Yes, before the model sees the data |
| Published price | Included in your Airtable plan | Your engineers' time | Contact sales | Free, Team from €99 |
| EU company | No | Whatever you are | Mostly US | Yes, Germany |
Native Airtable connector: Official Airtable MCP with OAuth or a personal access token. Whatever the signed-in person may see and change, including bases, schema and automations.
1 MintMCP, MCP Manager, Pomerium
Coming from one of them? Composio alternative · MintMCP alternative · MCP Manager alternative · AnythingMCP alternative
Also for
Connect another system to Claude
Before you connect.
- Does every team member need their own Airtable account?
- No. Loopthink holds one key or token for Airtable. Your people sign in to Loopthink with their own identity, and every call to Airtable is logged under their name. Seats in Airtable stay where they are today.
- Who has to add the connector in Claude?
- One person with the right to add connectors in your Claude workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.
- Where does the Airtable key live?
- In Loopthink, encrypted, in the EU. It never reaches Claude and never reaches the people using the connector. Rotate it in Airtable whenever you like and paste the new one once.
- Can somebody write to Airtable from the chat?
- Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.
- What does the model see?
- The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to Claude. The model gets the numbers, not the people.
- Is there an audit trail?
- Yes. Who asked, which tool, which parameters, which fields were masked, when. One log across every client your team uses, exportable for review.
- What does it cost?
- Free for one person and your own MCP server, forever. Team starts at €99 per month and covers the built connector, per-person identity, roles, masking and audit for the whole team. Prices are on the pricing page, no call needed.
- We already run our own MCP server for Airtable. Does it still work?
- Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.
Airtable in Claude, with rules.
One key in Loopthink, one login per person, one matrix that decides who may do what.
Free for your own server · Team from €99 · EU-hosted