Airtable

@airtable show me all records in the Product Roadmap base where status is 'In Progress' and priority is high

Found 7 records matching your criteria in the Product Roadmap base: 1. Mobile app redesign (Priority: High, Owner: Sarah Chen, Due: Feb 15) 2. API rate limiting improvements (Priority: High, Owner: Marcus Liu, Due: Feb 22) 3. Dashboard performance optimization (Priority: High, Owner: Priya Patel, Due: Mar 1) 4. SSO integration for enterprise (Priority: High, Owner: James Park, Due: Mar 8) 5. Webhook reliability fixes (Priority: High, Owner: Sarah Chen, Due: Mar 15) 6. Analytics export feature (Priority: High, Owner: Marcus Liu, Due: Mar 22) 7. Mobile push notifications (Priority: High, Owner: Priya Patel, Due: Apr 5) All items are currently in progress with assigned owners and target dates within the next 8 weeks.

This example demonstrates read-heavy querying with filters. The MCP requires OAuth2 scope for the specific base being accessed. Response shape and available fields depend entirely on your Airtable schema — this output assumes a typical roadmap structure with Status, Priority, Owner, and Due Date columns.

@airtable create 5 new records in our Customer Feedback table: one for each piece of feedback from today's user interviews, including contact email and sentiment

Successfully created 5 new records in the Customer Feedback table: • Record 1: Contact sarah.m@techcorp.com, Sentiment: Positive, Feedback: "Love the new dashboard layout" • Record 2: Contact james.k@startup.io, Sentiment: Neutral, Feedback: "Export feature works but could be faster" • Record 3: Contact priya.s@enterprise.com, Sentiment: Negative, Feedback: "Mobile app crashes on Android 13" • Record 4: Contact marcus.l@agency.co, Sentiment: Positive, Feedback: "API documentation is excellent" • Record 5: Contact emma.w@nonprofit.org, Sentiment: Neutral, Feedback: "Would like more customization options" All records are now visible in your Airtable base and available for filtering, sorting, and reporting.

This showcases bulk record creation, which is more efficient than individual creates. Field values must match your table's column types exactly (single-line text, email, single-select, etc.). If field types don't align, the operation fails. The MCP can create up to 10 records per request due to Airtable API limits.

@airtable review all comments on the Q1 Planning record and draft a summary of team concerns, then add that summary as a new comment

I reviewed 8 comments on the Q1 Planning record. Key themes: **Resource Constraints** (4 mentions): Team flagged insufficient engineering bandwidth for mobile and API work simultaneously. Sarah and Marcus both noted their teams are at capacity through March. **Timeline Concerns** (3 mentions): Priya questioned whether Feb 15 launch is realistic given current velocity. James suggested pushing enterprise features to Q2. **Dependency Risks** (2 mentions): Emma highlighted that analytics export depends on the unfinished dashboard work. I've added this summary as a new comment on the Q1 Planning record. The team can now reference this consolidated view instead of re-reading individual threads.

This example pairs the MCP's read capability (fetching comments) with AI synthesis, then writes back to Airtable. It demonstrates workflow automation — the AI acts as a meeting notes compiler. Requires comment read/write scope. Be aware that creating comments triggers Airtable notifications to collaborators, so this has side effects beyond data storage.

When Airtable MCP beats spreadsheets for support ops

A 6-person support team logs customer feedback in Airtable with tags, severity, and linked tickets. During weekly triage, the team lead asks Switchy to pull all high-severity items from the last sprint, create follow-up records for engineering, and post summary comments on each. The MCP's multi-record create and comment tools handle this in one prompt instead of 40 manual clicks. The OAuth2 setup means no API key rotation headaches. This works until you hit 500+ feedback items per week—at that scale, Airtable's rate limits start to bite and you'll want batch export instead. If your triage is under 200 records and you already live in Airtable, this MCP turns standup prep from 20 minutes to 2.

Why small content teams pick Airtable MCP for publishing workflows

A 3-person content team tracks blog posts, social threads, and email campaigns in a single Airtable base with linked records for authors and channels. The marketer asks Switchy to create next month's calendar skeleton—12 blog post records with draft titles, assigned writers, and placeholder publish dates—then add a comment on each flagging SEO keyword gaps. The MCP's create-multiple-records and create-comment tools make this a 30-second ask instead of a 15-minute copy-paste session. The create-field tool also lets you add new columns mid-sprint without leaving the chat. This breaks down if your calendar spans multiple bases or you need complex rollup formulas—Airtable's API doesn't expose those. For single-base publishing workflows under 50 assets per month, this MCP is the fastest path from idea to scheduled post.

When Airtable MCP simplifies recruiter handoffs at small scale

A 10-person startup tracks candidates in Airtable with stages, interview notes, and offer details. The hiring manager asks Switchy to move 5 candidates to 'Final Round', create interview schedule records for each, and post a comment tagging the recruiter with next steps. The MCP's update, create, and comment tools handle the full handoff in one prompt. OAuth2 means the manager's permissions flow through—no shared API key risk. This works cleanly until you're hiring for 10+ roles at once or need custom views per interviewer—at that point, Airtable's interface limits start to show and you'll want a dedicated ATS. For early-stage teams hiring 2-5 people per quarter, this MCP turns pipeline updates from a 10-minute admin task into a single conversational ask.