airtable-mcp-server

Created By
domdomegga year ago
🗂️🤖 Airtable Model Context Protocol Server, for allowing AI systems to interact with your Airtable bases
Overview

What is Airtable MCP Server?

Airtable MCP Server is a Model Context Protocol server that allows AI systems to interact with Airtable databases, providing read and write access to records and schemas.

How to use Airtable MCP Server?

To use this server, configure it in the "mcpServers" section of your claude_desktop_config.json file with your Airtable personal access token and run the server using the command: npx airtable-mcp-server.

Key features of Airtable MCP Server?

  • Read and write access to Airtable databases.
  • Ability to list records, search records, and manage tables and fields.
  • Provides detailed schema information for Airtable bases and tables.

Use cases of Airtable MCP Server?

  1. Integrating AI applications with Airtable for data management.
  2. Automating data entry and retrieval tasks in Airtable.
  3. Building custom applications that require dynamic interaction with Airtable data.

FAQ from Airtable MCP Server?

  • What permissions are needed for the Airtable token?

The token should have at least schema.bases:read and data.records:read permissions, with optional write permissions.

  • Can I use this server with other AI systems?

Yes! The server is designed to work with any AI system that supports the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
domdomegg
Star
158
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago