---
title: "Airtable MCP in Slack: ask an AI teammate to find and update records | Chickpea"
description: "Use Airtable's MCP server from Slack. Give a channel an AI teammate connected to Airtable, then ask it to find records, add one, or fix a field. Open source."
canonical: https://chickpea.co/connectors/airtable
keyword: "Airtable MCP in Slack"
verified: 2026-09-17
---

# An Airtable teammate in Slack, running on Airtable's MCP server.

> Chickpea gives a Slack channel a named AI teammate that holds its own Airtable connection. It signs in with OAuth and calls Airtable's MCP server, so there is no client to configure and no key to paste. Airtable's consent screen is where you choose which workspaces and bases the connection may reach, and the teammate never sees past that choice.

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/airtable; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**Airtable** (Formagrid Inc, https://airtable.com): Read and update records, bases, schemas, and comments. Category: Data and infrastructure. Lane: Vendor MCP server. Sign in: OAuth.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @pm, published to #ops.

### Find the records
- @pm which requests are still in review, and who owns each one
- @pm find every vendor row with no signed contract and a renewal this quarter

Say what you want to know and the teammate reads the base to answer it. Reads never need confirmation, and a long answer comes back as a table in the thread. Airtable says MCP permissions mirror the permissions you already have, so signing in does not widen anyone.

### Add a record from a thread
- @pm add this thread to Ops Requests as a new row, status Triage, owner Priya
- @pm create a record for the Vancouver printer order, due next Friday

A new record is a small, reversible write, so it goes straight through. The reply names the table, the fields it set, and what it left empty, with a link into the base. Airtable caps record creation at ten records per request, which is the limit on how much one ask can add.

### Fix a field or leave a comment
- @pm set REQ-204 to Approved and put Marco on it
- @pm comment on the Halvorsen row that the quote came in under budget

One field or one comment applies on the spot. The connection asks Airtable for read and write on records, schemas, and comments, and nothing else, so that is the whole of what a teammate can change.

### Change several rows at once
- @pm move every request still in Triage from August to Needs owner
- @pm set the region on the fourteen new vendor rows to EMEA

A change across several rows comes back as a list of what would move, and it waits for a yes. A write also needs the message you sent to name it, because thread history, a pasted document, and memory cannot authorize one on their own.

### On a schedule
- @pm every Monday at 9am Pacific, post the requests still in Triage
- @pm every weekday at 8am Eastern, list the rows due this week with no owner

A schedule saves on the spot. It needs an explicit time zone, runs under the Airtable connection of the person who asked, and fails with a named reason rather than running if that connection is disconnected.

### Example conversations

**Find the records**
> **Marco:** @pm which requests in Ops Requests are still in review, and who owns each one?
> **@pm:** Six rows are in review. Two of them have nobody on the Owner field.
>
> | Request | Team | Owner | Waiting on |
> |---|---|---|---|
> | REQ-198 | Finance | Priya | Vendor quote |
> | REQ-201 | Support | Dana | Legal |
> | REQ-204 | Eng | none | Owner |
> | REQ-207 | Eng | Marco | Budget code |
> | REQ-209 | Ops | none | Owner |

**Add a record**
> **Dana:** @pm add this thread to Ops Requests: the Vancouver office needs a second printer. Status Triage, owner Priya.
> **@pm:** Added REQ-214, Second printer for the Vancouver office. Status Triage, owner Priya, team Ops. I quoted this thread into Notes and left the due date empty, because nobody named one. Open it in Airtable

**Update several rows**
> **Sofia:** @pm every request still sitting in Triage from August should move to Needs owner.
> **@pm:** Nine rows match, all created in August, the oldest REQ-166 on Aug 4. Each would move from Triage to Needs owner and nothing else changes. That is a bulk write, so I will wait. Go ahead?
> Buttons: Yes, update all nine · Show me them first

**Every Monday**
> **Priya:** @pm every Monday at 9am Pacific, post the requests still in Triage here, with who raised each one.
> **@pm:** Saved. Every Monday at 9:00 AM Pacific I’ll list the Ops Requests rows still in Triage, with who raised each, in #ops. First run is Mon Sep 21. It runs on your Airtable connection, so say "pause the Monday digest" if you want it to stop.

## Connect Airtable
1. In Chickpea Admin, open the teammate, then **Connections**, find **Airtable**, and choose **Connect**. Or ask in Slack, `@pm connect Airtable`, and follow the link it posts.
2. Choose who uses it. **Team** is one shared Airtable account that everyone who can use the teammate acts through. **Personal** means each member signs in as themselves, and Airtable records their actions as them.
3. Choose **Continue to sign in**. Airtable's consent screen is where the reach is decided: one or more individual bases, every current and future base in named workspaces, or every base in every workspace. Pick the narrowest one that does the job.
4. Approve read and write on records, schemas, and comments. There is no token to paste and no config file to edit. Airtable keeps the grant on your third-party integrations page, where bases can be added or removed later.
5. Chickpea connects to [mcp.airtable.com/mcp](https://airtable.com/developers/agents/mcp/getting-started) and records the tools the server answered with. Ask something. `@pm which requests are still in review` is a good first question, because it reads and cannot change anything.

A connection belongs to one teammate. Giving a second teammate Airtable means a second sign-in with its own consent and its own choice of bases, so the support teammate never inherits the bases the ops teammate can reach.

## What the teammate is handed with Airtable
There is no built-in Chickpea skill for Airtable, and none is needed. The tools arrive from Airtable's MCP server: Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. Airtable groups what the server covers into creating and discovering bases, changing a base schema, reading and writing records, and creating and managing automations. Chickpea asks for read and write on records, schemas, and comments, plus reading the list of workspaces and bases, so that grant is the ceiling on what a teammate can use.

Airtable documents the server, its scopes, and the clients it supports: https://airtable.com/developers/agents/mcp/getting-started

## Beside Airtable
- **Asana:** An intake row in the base becomes an owned task with a due date
- **Notion:** The base holds the records, Notion holds the write-up that quotes them
- **HubSpot:** A vendor or partner row read beside the deal it belongs to
- **Google Sheets:** A base for the work that repeats, a sheet for the numbers that do not
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### Is there an Airtable MCP server?
Yes. Airtable runs a hosted MCP server at mcp.airtable.com/mcp, with OAuth sign-in or a personal access token, and it is available to all users on all plans at no extra charge. Airtable documents setup for Claude, ChatGPT, Cursor, and other MCP clients. Chickpea connects to that same server with OAuth, which is how a teammate in Slack uses it with no client installed.

### How do I set up the Airtable MCP?
For a coding client or a chat client, follow Airtable's own docs, since each one keeps its own config. For Slack there is nothing to configure. Open the teammate in Chickpea Admin, choose Airtable, choose Continue to sign in, and pick the bases on Airtable's consent screen. Or ask "@pm connect Airtable" in the channel and follow the link it posts.

### Does it use Airtable's MCP server or the API?
The MCP server. Airtable is a vendor MCP lane: the deployment connects to mcp.airtable.com/mcp over streamable HTTP and signs in with OAuth. There is no API key and no personal access token anywhere in this connector, and the connection cannot reach any other address.

### Which bases can it see?
The ones you approved when you signed in. Airtable lets you grant one or more individual bases, every current and future base in named workspaces, or every base in every workspace, and the grant can be edited later on your third-party integrations page. Airtable also says MCP permissions mirror the permission level you already hold, so the teammate cannot outrun the account it signed in as. In Chickpea the binding is a ceiling: it can be narrowed to fewer tools but never widened, and reauthorizing Airtable with more bases does not widen the teammate.

### Can it delete records?
Airtable describes the server as covering creating and discovering bases, changing base schema, reading and writing records, and creating and managing automations, and publishes no tool list, so this page will not claim one way or the other about what exists. What is fixed is the scope and the gate. The connection carries read and write on records, schemas, and comments, and nothing else. During a Slack turn Chickpea refuses any MCP tool whose name does not start with an unambiguous read verb unless the message you just sent names that action.

### Where does the OAuth token live?
On your deployment, outside the teammate record. It never enters the model's context, the tool arguments the model writes, or Slack. The model picks a connection by id and the credential goes in at the last step on the way out. Who it belongs to is your choice when you connect: a team account is one shared sign-in that everyone with access to the teammate acts through, and a personal account is used only for your own requests. Disconnect the account and the stored secret is removed, and any schedule that depended on it stops.

### Do I still need Airtable's Slack integration?
Often yes, because it does things a teammate does not. Airtable's Slack app posts messages when records change, sends messages from an automation to a channel, and shows a rich preview when someone pastes a record link. It also has an AI assistant you @mention to ask about a base, summarize it, and create or update records, on all plans, with each person linking their own Airtable account. Airtable caps that assistant at 50 records and five messages per response, and only the person who started a thread can continue it. A Chickpea teammate hears nothing from Airtable and posts nothing unprompted. What it adds is schedules, saved instructions, several connected accounts in one teammate, and the whole thing running on your own Cloudflare account.

### Which Airtable plan does this need?
None in particular. Airtable says the MCP server is available to all users on all plans, with no additional Airtable charge, though calls count against the standard API rate limits. Setting one up takes an Owner, Creator, or Editor role; a read-only or commenter role can only read. What the teammate can see and change is what the account you signed in with can see and change.

### Can Airtable integrate with Slack?
Two ways. Airtable ships its own Slack app for notifications, automation messages, record previews, and an AI assistant you @mention. A Chickpea teammate is the other way: it holds an Airtable connection of its own and does what you ask in the channel, through Airtable's MCP server. They do different jobs, and both can be installed.

### Can I use this from Claude Code or Cursor instead?
Yes, and Airtable documents both. Those put the server in one person's editor. A teammate puts it in a channel, with a stored connection, saved instructions, schedules, and every change visible in the thread where someone asked for it. Teams often run both.

## Sources
- [Chickpea docs: connector catalog, the Airtable preset, its lane and OAuth scope](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: connections, team and personal accounts, the binding as a ceiling](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation, including the read-verb gate](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service, OAuth presets and the Slack link](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules, time zones and what each run rechecks](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the Airtable preset (server URL, transport, OAuth scope)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Chickpea source: an MCP connection exposes approved tools that are still discovered](https://github.com/pejmanjohn/chickpea/blob/main/src/config/types.ts)
- [Airtable developers: the MCP server, its URL, OAuth scopes and what it covers](https://airtable.com/developers/agents/mcp/getting-started)
- [Airtable support: using the MCP server, plans, roles and the ten-record cap](https://support.airtable.com/articles/9897799762-using-the-airtable-mcp-server)
- [Airtable: the Slack integration, its notifications, previews and AI assistant](https://www.airtable.com/integrations/slack)
- [Airtable support: using Airtable AI in Slack, and its limits](https://support.airtable.com/articles/1650918322-using-airtable-ai-in-slack)
- [Airtable terms of service, where the legal entity behind Airtable is named](https://www.airtable.com/company/tos)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Asana AI agent in Slack](https://chickpea.co/connectors/asana.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gamma MCP in Slack](https://chickpea.co/connectors/gamma.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Gong AI agent in Slack](https://chickpea.co/connectors/gong-managed.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [Granola MCP in Slack](https://chickpea.co/connectors/granola.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [Linear MCP in Slack](https://chickpea.co/connectors/linear.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [PostHog MCP in Slack](https://chickpea.co/connectors/posthog.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co