Airtable vs Microsoft Excel (Microsoft Graph workbook API)

Airtable

Tokens are limited by scope and by base, and the official MCP server at mcp.airtable.com covers records, schema, interfaces and automations in 40 tools. The REST API allows 5 requests a second per base with a 30-second lockout after a 429, writes take 10 records a call, and the Free plan stops at 1,000 calls a month.

Microsoft Excel (Microsoft Graph workbook API)

Ranges, tables, charts and 366 worksheet function endpoints are reachable over REST with a public OpenAPI, and a non-persistent session lets an agent test changes without saving them. The reference pages list delegated permissions only, with Files.ReadWrite as the least privileged scope, and writes take no idempotency key.

Airtable

1. Create a personal access token with only the scopes needed and add each base to it. A token with no base added sees nothing
2. Stay under 5 requests a second per base. After a 429, wait 30 seconds before the next call
3. Send writes in batches of 10 records, and use performUpsert with fieldsToMergeOn so a repeated call updates instead of duplicating
4. Use table and field IDs, not names, and set returnFieldsByFieldId so a rename doesn't break the call
5. POST to /listRecords when a filterByFormula would push the URL past 16,000 characters

Microsoft Excel (Microsoft Graph workbook API)

1. Create a session with POST /workbook/createSession and send workbook-session-id on every call. Persistent sessions expire after about 5 minutes idle
2. Set persistChanges to false when you only need a calculation or a chart image, so nothing is saved to the file
3. Send one request at a time per workbook and wait for each response. Microsoft warns that parallel writes cause throttling, timeouts and merge conflicts
4. Add rows in one call with a two-dimensional values array, and check the table before repeating a row add that returned 504
5. Read bounded addresses such as A1:D500. A whole-column range such as C:C returns null for values, and writes to it are refused