Connect Airtable to VS Code
Give VS Code governed access to Airtable’s 46 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Airtable to VS Code in four steps
Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.
- 1
Approve Airtable in Runlayer
Add Airtable from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect VS Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Airtable’s 46 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 3
Sign in to Airtable
Each user signs in to Airtable with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Airtable from VS Code
Airtable’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
46 Airtable tools in VS Code
Runlayer policy decides which of these VS Code users can call. 6 read data only and 1 can change or delete data.
Analyze table
Run statistical operations (count, sum, average, min, max, etc.) on an Airtable table, optionally grouped by columns and filtered.
Create automation
Creates and validates one automation in a base: a trigger plus ordered nodes — action nodes, repeatingGroup (run inner nodes once per item), and conditionalGroup (if/else-if/else branches).
Create base
Creates a new Airtable base with the specified tables and fields.
Create field
Creates a new field in an existing Airtable table.
Create interface
Creates a new interface within a base.
Create page
Creates a new page.
Create record comment
Creates a comment on a specific Airtable record.
Create records for table
Creates new records in an Airtable table.
Control
What Runlayer can see and stop in VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every Airtable call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before VS Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before VS Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.
Frequently asked questions
Connect more
