/ 디렉터리 / 플레이그라운드 / airtable-mcp-server
● 커뮤니티 domdomegg ⚡ 바로 사용

airtable-mcp-server

제작: domdomegg · domdomegg/airtable-mcp-server

Read and edit Airtable from chat — with a fine-grained PAT that scopes exactly which bases the AI can touch.

airtable-mcp-server by domdomegg is the community-standard Airtable MCP. Authenticates with an Airtable Personal Access Token, exposes 15+ tools for records/tables/fields/comments, and can be pinned to read-only via PAT scopes. Works with any Airtable base including enterprise workspaces.

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

airtable.replay ▶ 준비됨
0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "airtable": {
      "command": "npx",
      "args": [
        "-y",
        "airtable-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "airtable": {
      "command": "npx",
      "args": [
        "-y",
        "airtable-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "airtable": {
      "command": "npx",
      "args": [
        "-y",
        "airtable-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "airtable": {
      "command": "npx",
      "args": [
        "-y",
        "airtable-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "airtable",
      "command": "npx",
      "args": [
        "-y",
        "airtable-mcp-server"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json
{
  "context_servers": {
    "airtable": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "airtable-mcp-server"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add airtable -- npx -y airtable-mcp-server

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: airtable-mcp-server

Answer natural-language questions about your Airtable CRM

👤 Founders and ops people using Airtable as a CRM ⏱ ~10 min beginner

언제 쓸까: You want to know 'who hasn't replied in 30 days?' without building a view.

사전 조건
  • Airtable PAT with schema.bases:read + data.records:read — airtable.com/create/tokens/new — pick only the bases you want exposed
흐름
  1. Have Claude list bases and pick the right one
    List my Airtable bases. Find the one that looks like a sales CRM and describe its tables.✓ 복사됨
    → Schema of the CRM base with table purposes
  2. Ask the real question
    In the Contacts table, find people where Last Contacted is more than 30 days ago and Status is Active. Group by Owner.✓ 복사됨
    → Filtered record list by owner
  3. Draft follow-up actions
    For each contact, draft a one-line nudge email I can send. Match their last conversation's tone.✓ 복사됨
    → Per-contact draft text

결과: A next-action list straight from the CRM in 2 minutes.

함정
  • Linked-record fields return IDs, not names — Ask Claude to resolve linked records via a second fetch, or use list_records with returnFieldsByFieldId=false
  • Enterprise bases often have permission restrictions per-field — Verify your PAT's workspace access matches the base's enterprise policy
함께 쓰기: notion

Bulk-clean messy Airtable records

👤 Ops admins inheriting a chaotic base ⏱ ~45 min intermediate

언제 쓸까: A table has 3k rows with inconsistent casing, missing fields, duplicate companies.

사전 조건
  • PAT with data.records:write — Add the scope when creating the token; keep base scope narrow
흐름
  1. Audit the mess
    In Companies, find duplicates by normalized name, records missing Domain, and records with Website starting with http:// instead of https://.✓ 복사됨
    → Count per issue
  2. Dry-run a fix plan
    For each issue, propose a fix and show me 3 example changes BEFORE writing.✓ 복사됨
    → Preview with user approval gate
  3. Apply the approved fixes
    Approved. Apply the fixes in batches of 50 with update_records.✓ 복사됨
    → Success counts per batch

결과: A clean table with an auditable list of what changed.

함정
  • Mass-updating triggers Airtable's per-token automation quotas — Batch at 10/s max; pause automations for the affected table during bulk ops
  • One bad update pattern ruins 500 rows — Snapshot the table (CSV export) before the first write
함께 쓰기: filesystem

Use Airtable as a headless CMS for a website

👤 Indie devs and content teams ⏱ ~30 min intermediate

언제 쓸까: You want editors in Airtable and publishing logic driven by an agent.

흐름
  1. Pull publish-ready records
    From the Blog table, list records where Status is 'Ready' and PublishDate is today or earlier.✓ 복사됨
    → Publish queue
  2. Transform and emit
    For each, convert the rich-text Body field to Markdown and write to /site/content/posts/<slug>.md.✓ 복사됨
    → Files appear on disk
  3. Flip the status back
    Update each record's Status to 'Published' and set PublishedAt to now.✓ 복사됨
    → Rows flipped

결과: A one-command publish flow with Airtable as source of truth.

함께 쓰기: filesystem · github

조합

다른 MCP와 조합해 10배 효율

airtable + notion

Turn an Airtable report into a Notion briefing

Pull this week's new Deals from the CRM, then create a Notion page in /Sales with a summary table.✓ 복사됨
airtable + filesystem

Use Airtable as a CMS, emit Markdown files

For every Blog record with Status=Ready, write a .md file under ./content/posts/ and flip the record to Published.✓ 복사됨
airtable + github

Auto-create GitHub issues from an Airtable bug backlog

For every Bug in the Triage view with Severity=High, open a GitHub issue in acme/api with title and repro steps.✓ 복사됨

도구

이 MCP가 노출하는 것

도구입력언제 호출비용
list_bases (none) First-time discovery 1 API call
list_tables baseId: str, detailLevel?: str Map a base before querying 1 API call
describe_table baseId: str, tableId: str Know the fields before filtering 1 API call
list_records baseId, tableId, view?, filterByFormula?, sort?, pageSize? Read data with filters/sort 1 API call (paginates)
search_records baseId, tableId, searchTerm, fieldIds? Free-text search across fields 1 API call
get_record baseId, tableId, recordId Fetch a single known record 1 API call
create_record baseId, tableId, fields Insert one record 1 API call (write)
update_records baseId, tableId, records[] Batch updates 1 API call per 10 records
delete_records baseId, tableId, recordIds Destructive — confirm first 1 API call (write)
create_table baseId, name, fields[] Bootstrap a new data model 1 API call (schema write)
list_comments baseId, tableId, recordId, offset?, pageSize? Read thread history 1 API call

비용 및 제한

운영 비용

API 쿼터
5 requests/sec per base (Team), 50/sec on Enterprise Scale
호출당 토큰
Schema: ~500 tokens. Record responses: 200 tokens per row depending on fields.
금액
Airtable free/Team/Enterprise — API access on all paid plans; free plan also exposes API
Use pageSize and filterByFormula server-side; pulling a whole table into context is wasteful.

보안

권한, 시크릿, 파급범위

최소 스코프: schema.bases:read data.records:read
자격 증명 저장: Fine-grained PAT in env var AIRTABLE_API_KEY; never classic user tokens
데이터 외부 송신: All calls to api.airtable.com over HTTPS
절대 부여 금지: All-base access when only one base is needed webhook:manage unless required

문제 해결

자주 발생하는 오류와 해결

401 INVALID_API_KEY

PAT missing or expired. Regenerate at airtable.com/create/tokens.

확인: curl -H 'Authorization: Bearer $AIRTABLE_API_KEY' https://api.airtable.com/v0/meta/bases
403 NOT_AUTHORIZED

PAT doesn't include that base. Edit the token's scope list and add the base.

확인: curl returns bases you expect
422 INVALID_REQUEST_UNKNOWN_FIELD

Field name doesn't match schema. Re-describe the table — Airtable changes field IDs if renamed.

확인: call describe_table again
429 rate limit

Slow down to 5 req/sec per base; batch write operations.

확인: retry after 30s

대안

airtable-mcp-server 다른 것과 비교

대안언제 쓰나단점/장점
Notion MCPYour team lives in Notion databases instead of AirtableNotion is less tabular; worse for bulk data ops
Google Sheets MCPThe data is in SheetsNo structured schema or linked records
Direct Airtable REST via fetch MCPYou want one-off calls and don't want another MCPYou write every URL by hand

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기