recent_changes — Airtable MCP Tool
recent_changes
(recent changes) is one of 41 tools on the
Airtable
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call recent_changes from your client
- Claude Code Airtable recent_changes run in your project directory
- Claude Desktop Airtable recent_changes ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Airtable recent_changes ~/.cursor/mcp.json
- VS Code Airtable recent_changes .vscode/mcp.json
- Zed Airtable recent_changes ~/.config/zed/settings.json
- Windsurf Airtable recent_changes ~/.codeium/windsurf/mcp_config.json
- Cline Airtable recent_changes ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Airtable recent_changes ~/.gemini/settings.json
- Grok Airtable recent_changes .mcp.json (in your project root)
- ChatGPT Airtable recent_changes Settings → Connectors → Advanced → Developer mode
- Claude.ai Airtable recent_changes Settings → Connectors → Add custom connector
- LangChain Airtable recent_changes pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http airtable https://gateway.pipeworx.io/airtable/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- airtable_list_records
- airtable_get_record
- airtable_create_record
- airtable_list_bases
- airtable_get_base_schema
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.