01 · Records and state owned
Workspaces, bases, tables, schemas, records, comments, Interface pages, and records exposed through pages a user can access.
Airtable
Airtable
Curated anchor platform in collaborative database and app platform with material relevance to the Marcom operating stack and a first-party developer surface.
Work & collaborationSystem of coordinationExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Workspaces, bases, tables, schemas, records, comments, Interface pages, and records exposed through pages a user can access.
03 · Actions and write paths
Create bases, tables, fields, records, Interfaces and Interface pages; update records/tables/fields; publish Interfaces; and delete Interface pages through documented tools.
04 · Authentication and permissions
OAuth is recommended; personal access tokens and enterprise read-only service-account patterns are also documented. MCP mirrors Airtable permission levels. Owners/creators/editors can write within their grants; commenters/read-only users can read. Enterprise service accounts can be scoped read-only.
05 · Monitoring, approval, and recovery
Require confirmation before schema changes, Interface publication, deletions, bulk record writes, or access to sensitive bases. Editing existing Interface pages is not currently supported. Tool availability can depend on client support, organization allowlisting, and granted bases/scopes.
06 · Gaps and implementation limits
Editing existing Interface pages is not currently supported. Tool availability can depend on client support, organization allowlisting, and granted bases/scopes.
Agent access
MCP and adjacent posture
Verified first-party provider MCPAirtable hosted MCP and interactive-app surfaceCurrent documented service
Role: provider
Read scope: Workspaces, bases, tables, schemas, records, comments, Interface pages, and records exposed through pages a user can access.
Write scope: Create bases, tables, fields, records, Interfaces and Interface pages; update records/tables/fields; publish Interfaces; and delete Interface pages through documented tools.
Authentication: OAuth is recommended; personal access tokens and enterprise read-only service-account patterns are also documented.
Approval boundary: Require confirmation before schema changes, Interface publication, deletions, bulk record writes, or access to sensitive bases.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Airtable ships these experiences.
Single-platform patterns
- Custom campaign operations database and UI
- Marketing launch room
- Agent supervision inbox
- Cross-functional approval workspace
Multi-platform compositions
- Airtable + campaign or CRM system: marketing launch room
- Airtable + content-production platform + analytics or automation system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCP / agent-role validationRepresentative source
https://support.airtable.com/docs/using-the-airtable-mcp-server ↗Airtable documents a hosted MCP for data, schema, and Interface workflows, with OAuth or narrowly scoped personal-access-token options.
- Publisher published
- Feb 11, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://airtable.com/developers/web/api/introduction ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://airtable.com/developers ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://airtable.com/developers/web/api/webhooks-overview ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.airtable.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.