Think inside your AI world.
How do I connect Airtable to Claude?
Airtable over MCP means Claude reads your bases as structured records — filters, fields, views — not as screenshots of tables.
Direct answer: add Airtable's MCP server in Claude (Settings → Connectors, authorise; Claude Code via 'claude mcp add'). Claude then works with structured records — reading and, where you allow it, writing — so a base stops being a tab you check and becomes data the conversation can query directly.
Bases as a conversational surface
Which records match this filter, what changed in the content calendar this week, which grant deadlines fall inside thirty days — answered against live fields. Structured access is the point: the model reasons over records, not over a rendering of them.
The standard the base doesn't apply to itself
Editorial case: your desk ratified a two-source rule — nothing moves to 'ready to publish' without two independent sources logged — after a correction that still stings. Airtable stores the source fields; whether a record honours the rule is a reading of the record, and the base does not read itself.
Records read against the rule
Through Unl, the pipeline read arrives adjudicated: two pieces sit at ready with one source logged — short of the standard you set after the March correction. The check that relied on an editor's tired eyes at 6pm becomes structural. The rule's memory — why it exists — travels with every flag.
Airtable to Claude turns bases into queryable records; through Unl those records are read against the editorial and operational standards you ratified, so exceptions surface themselves.
Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Read further
Questions people ask
What does the Airtable MCP server allow?
Structured read and write over your bases — records, fields, filters. What Claude may touch follows from what you authorise; a read-only posture works fine for review and reporting flows.
Is this the same for ChatGPT?
Yes — one MCP server, many clients. The connection steps mirror this page's; only the settings menu differs by product.
What rules suit an Airtable-run workflow?
Stage-gate standards: what a record needs before it advances — sources logged, owner assigned, review date set. Ratified with the incident that created them, they turn every pipeline read into quality control.
What if the base's columns change under the rule?
A rule written about a column name breaks the moment someone renames it. Write it about the thing instead — the state a record is in, the condition that makes it an exception — so it survives the schema drift that Airtable bases are especially prone to.
What this is
Think inside your AI world — you stay in command
Save the thoughts, decisions and targets worth keeping, each with its reasoning, carried into every AI session the moment they matter. A new unit of exchange between you and your AI: the Settled Why with standing that travels. Unprompted.
Your whole AI world. What you decided at the epicentre. It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector — quick to connect, in a couple of steps.
MCP native·Human settled·Model agnostic·Your data
Measured Context
Connect Unl to bring the right information into the moment.
Your sources, read against the criteria you set.
The full product, open. Free at launch.