Share Airtable MCP tools.
Bases and records for remote teammates — every visible base is readable.
Run on your machine
Start the server on your host machine. Tools not listed in --allow are completely hidden from the agent.
npx -y @mcpwire/cli share \
--name airtable \
--allow "list_bases,list_tables,describe_table,list_records,search_records,get_record,list_comments" \
--redact-secrets \
-- npx -y airtable-mcp-server@1.14.0
Exposes 7 default tools with pattern-based secret redaction.
Optionally set an expiry with --ttl 30m, prompt for approvals with --confirm, or limit calls with --max-calls 20.
Connect your teammate’s agent
MCPWire prints a unique wire://... ticket in your terminal. Send it privately to your teammate to paste into their MCP client:
{
"mcpServers": {
"airtable": {
"command": "npx",
"args": [
"-y",
"@mcpwire/cli",
"join",
"wire://<TICKET_FROM_HOST>"
]
}
}
}
Replace <TICKET_FROM_HOST> with the active session ticket. The agent can only discover and call the tools exposed above.
Scoped tool permissions
MCPWire acts as a Layer 7 JSON-RPC firewall. Requests for blocked tools are dropped on the wire before ever touching your machine.
| Tool | Default Policy | Notes |
|---|---|---|
list_bases | Allowed | Lists bases the token can reach. |
list_tables | Allowed | Lists tables in a base. |
describe_table | Allowed | Reads table schema and field definitions. |
list_records | Allowed | Reads records — cell contents go to the guest. |
search_records | Allowed | Searches record text. |
get_record | Allowed | Reads one record. |
list_comments | Allowed | Reads record comments. |
create_record | Blocked (High risk) | Inserts records. |
update_records | Blocked (High risk) | Modifies records, with bulk support. |
delete_records | Blocked (High risk) | Deletes records. |
create_table | Blocked (High risk) | Creates tables. |
update_table | Blocked (High risk) | Changes table names and descriptions. |
create_field | Blocked (High risk) | Adds columns. |
update_field | Blocked (High risk) | Modifies column definitions; type changes can reformat data. |
create_comment | Blocked (High risk) | Posts comments as your identity. |
Test and verify
Try these recommended prompts to confirm the agent receives expected outputs and that restricted actions fail safely.
Try Airtable
Create a personal access token scoped to just the bases you want to share, and set AIRTABLE_API_KEY in the host environment. Airtable tokens can’t be restricted per operation — a token that can read a base can also write to it — so the base scope is the real security boundary.
Ask the agent what it can see with list_bases, then explore with list_tables and list_records. Record contents, comments, and schemas flow to the guest while the session is open. All mutating tools (create_record, update_records, delete_records, schema changes, comments) stay outside the default allowlist. This is the most widely used community Airtable server.
The generated command above contains the catalog’s explicit default allowlist. Check the guest’s tool list before making calls and use the server’s argument schema for required fields. See the CLI guide for guest configuration and session controls for approvals, redaction, and expiry.
--record session.wirelog to your host command. Drop the resulting file into the Session Replay Viewer to inspect timestamps, latency, blocked attempts, and secret scrubbing.