Airtable MCP Pro
Airtable MCP Pro (Coolify-ready)
Vollständiger Airtable-Connector über MCP für ChatGPT Business / Projects.
Tools:
list_bases,list_tables,list_fields,query,search,fetch,create,update,delete,upsertPagination (
pageSize,offset), Sortierung,filterByFormula,fields[],viewRate-Limit-Handling (429 Retry mit Backoff), Logging
Token-Strategie: Per-User via
X-User-Tokenoder Workspace-DefaultAIRTABLE_TOKEN
Env
PORT=3000
AIRTABLE_TOKEN=pat_xxx # Fallback; bevorzugt X-User-Token Header
AIRTABLE_BASE_ID=appXXXX # optional Default base
AIRTABLE_TABLE=YourTable # optional Default table
MCP_AUTH_TOKEN=change-me # optional Connector-Bearer
LOG_LEVEL=infoLocal run
npm ci
npm run dev
# health
curl http://localhost:3000/health
# list bases (requires token)
curl -X POST http://localhost:3000/mcp -H "Content-Type: application/json" -H "X-User-Token: $AIRTABLE_TOKEN" -d '{"tool":"list_bases","input":{}}'
# query with defaults
curl -X POST http://localhost:3000/mcp -H "Content-Type: application/json" -H "X-User-Token: $AIRTABLE_TOKEN" -d '{"tool":"query","input":{"pageSize":5}}'Deploy (Coolify)
Neues App (Dockerfile)
ENV setzen (
AIRTABLE_TOKENoptional,MCP_AUTH_TOKENoptional, Defaults)Domain/SSL →
GET /healthsollte{ ok: true }liefernChatGPT Business → Settings → Connectors → Create → URL
https://<domain>/mcpWenn
MCP_AUTH_TOKENgesetzt: als Bearer im Connector hinterlegenPublish → im Projekt aktivieren
Tools & Inputs (JSON)
list_bases→{}list_tables→{ "baseId": "app..." }list_fields→{ "baseId": "app...", "tableIdOrName": "tbl...|Name" }query→{ "baseId"?, "table"?, "view"?, "fields"?, "filterByFormula"?, "sort"?, "pageSize"?, "offset"? }search→{ "query": "...", "baseId"?, "table"?, "field"?, "formula"?, "view"?, "fields"?, "sort"?, "pageSize"?, "offset"? }fetch→{ "recordId": "rec...", "baseId"?, "table"? }create→{ "records": [{ "fields": {...}}], "baseId"?, "table"?, "typecast"? }update→{ "records": [{ "id": "rec...", "fields": {...}}], "baseId"?, "table"?, "typecast"? }delete→{ "recordIds": ["rec..."], "baseId"?, "table"? }upsert→{ "mergeField": "Email", "records": [{ "fields": {...}}], "baseId"?, "table"?, "typecast"? }
Hinweise
Per-User-Auth: Der Connector kann im Request-Header
X-User-Tokeneinen PAT entgegennehmen (z. B. von ChatGPT gespeicherte User-Creds). Ohne diesen nutzt erAIRTABLE_TOKEN.Attachments: Über
create/updatekannst du Attachments per URL in ein Feld vom Typ „Attachment“ schreiben ({ fields: { Attachments: [{ url: "https://..." }] } }).Upsert: Nutzt
mergeField(eindeutig!), holt bestehende Records und splittet in Create/Update.Limits:
pageSize≤ 100. Nutze die zurückgegebeneoffset, um zu paginieren.
Happy building 🚀
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/IngoKiy/airtable-mcp-ik'
If you have feedback or need assistance with the MCP directory API, please join our Discord server