Connect MCPs. Build in one place
MCP lets an AI agent reach into the tools you already use and do the work — not just talk about it.
I let an AI agent build Airtable bases through the API, and flag what I must finish by hand.
I build a lot of Airtable bases — for myself and for clients — and an AI agent with API access can do most of it in one pass. But the API has hard walls: it can create fields but never delete them, it can't edit a dropdown's options, and it can't make lookups, rollups, or counts.
Ignored, those become silent landmines — a plain-number stand-in where a currency rollup should be, and your numbers are quietly wrong. So I make every unfinished thing loud: the agent marks each one, and I clean it up in two minutes. The whole convention is two colours — a yellow 🟡 marker for "fix this", a red 🔴 marker for "delete this".
Build in minutes, not hours — the agent does the repetitive 80% of schema-building in one pass.
Nothing breaks silently — every limit the API hits becomes a visible marker, not a hidden wrong-typed field.
A two-minute human finish — you do only the handful of clicks the API genuinely can't, guided to exactly where.
Formulas survive the cleanup — converting a placeholder keeps its field ID, so dependent formulas keep working untouched.
Reusable on every base — the same convention works for any AI-built Airtable, yours or a client's.
Hover a step to open it, or click to toggle.
Describe the base in plain English — the tables, what links to what, the formulas you want. Give the agent a scoped API key and let it create the tables, fields, links, and any formulas it can. This is the fast 80%.
Never hand off a marker silently — the agent should list every 🟡 and 🔴 it left, and what each one needs, in the same message.
Test on a throwaway table first — verify what your API key can and can't do against a scratch table before it touches real schema.
Renaming is always safe — Airtable references fields by ID, so renaming a table or field never breaks a link, lookup, or formula.
Mind the rate limit — Airtable allows about five API calls a second per base; big rename sweeps need a small pause between calls.