Skip to main content
Book a demo

Connect Airtable to Cline CLI

Give Cline CLI governed access to Airtable’s 46 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add Airtable to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 1

    Approve Airtable in Runlayer

    Add Airtable from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Airtable’s 46 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to Airtable

    Each user signs in to Airtable with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Airtable from Cline CLI

    Airtable’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

46 Airtable tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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.

See all 46 Airtable tools

Control

What Runlayer can see and stop in Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Airtable call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI 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 Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination