Head to head · Spreadsheet access · October 2026 research run
Microsoft Excel (Microsoft Graph workbook API) vs NocoDB
NocoDB scores 74.6 (BB) on agent readiness against Microsoft Excel (Microsoft Graph workbook API)'s 53.9 (D), and leads in 6 of 7 scored categories. Both do spreadsheet access.
Best spreadsheet and operational table APIs for AI agents · All 45 spreadsheets comparisons
Which one, for what
Microsoft Excel (Microsoft Graph workbook API) D
Best for Agents working on .xlsx files that already live in a Microsoft 365 tenant, and for using Excel's calculation engine through function endpoints.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Reference pages list delegated permissions only and mark application permissions as not supported
NocoDB BB
Best for Teams that want Airtable-style typed records with the option to self-host, and an agent that reads, filters and writes records or builds schema through MCP with a narrow allowlist.
Ahead on
- Reliability, 97 against 69
- Security & auth, 71 against 63
- Payments & pricing, 45 against 23
- Maintenance & community, 87 against 33
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
5 requests a second per user on every plan, shared by all of that user's tokens, with a 30-second block after a 429
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community NocoDB +54
Microsoft Excel (Microsoft Graph workbook API) 33
Graph SDKs bundle every Graph product, so only releases that change workbook code count, as groq-speech-to-text and vonage-voice read umbrella SDKs. In clones on 4 November, the last msgraph-sdk-python release changing workbook request builders or models is v1.59.0 (10 July 2026), and the last .NET one 6.3.0 (10 July 2026). v1.61.0 to v1.65.0 (5 August to 22 October) and .NET 6.5.0 to 6.9.0 change no workbook file, and the last Workbooks and charts entry in the Graph changelog is dated 19 September 2025. Last change 117 days ago (10). No release or dated changelog entry touching workbooks since 6 August (0). A public changelog and SDK issue trackers. The seven newest open issues on msgraph-sdk-python had no or one reply on 8 October, and two security fixes merged into the JavaScript client (16 June and 15 October 2026) haven't reached a release (7). Current SDKs in most languages, with the JavaScript client the exception at 3.0.7 from September 2023 (10). Active releases on the Python package, none on the JavaScript one (6). 10+0+7+10+6 = 33.
NocoDB 87
Release 2026.10.1, tagged on 28 October 2026, after 2026.10.0 on 23 October (30). Seven release tags in the 90 days from 3 August, from 2026.08.0 on 4 August to 2026.10.1 (20). 387 open issues on GitHub, the 25 newest opened between 11 July and 7 October 2026, per the 8 October check. GitHub's issue pages weren't read on 1 November and we didn't read reply times (14 of 25). Not in the official MCP registry, where a search for nocodb still returns nothing on 1 November. nocodb-sdk 0.301.3 was the latest on npm per the 17 October check, and npm did not resolve from our shell on 1 November (15). The repository has unit test, build check and dependency review workflows and a Renovate config, with the newest commit on the develop branch on 31 October 2026. We didn't read the workflow results (8 of 10).
Reliability NocoDB +28
Microsoft Excel (Microsoft Graph workbook API) 69
A public Microsoft service health page at status.cloud.microsoft (20). It answered robots.txt with an empty 401 on 1 November 2026, so it is treated as blocked and wasn't read; on 8 October it needed JavaScript, so no incident history has been readable (5). Excel resources are throttled at 5,000 requests per 10 seconds per app across all tenants and 1,500 per app per tenant, under a global 130,000 per 10 seconds (throttling limits page updated 17 September 2026), though Microsoft adds that the cost of a workbook call varies too much for the numbers to tell the whole story (15). Throttled responses carry Retry-After, the error guide gives a retry instruction per error code, and Microsoft asks for one request at a time per workbook. There is no idempotency key, and the row-add page says to repeat the request on a 504, which can add rows twice (12). The November 2026 Online Services SLA has no Graph entry. Its Office Online level counts downtime when users can't use the Web Applications to view and edit an Office document stored on SharePoint Online, 99.9 per cent with 25, 50 and 100 per cent credits. That level measures the editing the workbook API does, through a named client, read as outlook-mail-graph and microsoft-teams (7). The workbook endpoints are generally available on v1.0 (10). 20+5+15+12+7+10 = 69.
NocoDB 97
Graded on NocoDB Cloud (the v3 REST API and the built-in MCP server) with the hosted lines. Status page at status.nocodb.com on Kener, with two components and 90-day availability per the 8 October check. Its components render by script and weren't re-read after 8 October (20). The monthly incident pages read on 8 October now return 400 or 404. The incidents and maintenance RSS feed, re-read on 1 November (built 1 November 05:10 GMT), holds no item, and on 8 October no incident was listed for July to October 2026 (30). 5 requests a second per user on all plans, monthly API call allowances per plan, 10 records per REST write and 100 per MCP record call, and since 2026.10.1 MCP has its own limit per account that tells a client how long to wait (15). A 429 means waiting 30 seconds per the docs and carries Retry-After per the OpenAPI file, and upsert on a merge key makes a repeated write safe. No idempotency keys (12). A 99.9 per cent monthly uptime commitment is published for Enterprise plans, the SLA page still dated 6 October 2025 (10). The v3 API and the MCP server carry no beta label, while the pricing page marks the v2 APIs 'will deprecate soon' (10).
Payments & pricing NocoDB +22
Microsoft Excel (Microsoft Graph workbook API) 23
No x402, MPP or L402 (0). Workbook calls aren't on Microsoft's metered API list, so there is no per-call charge, but the file's home needs a Microsoft 365 licence and the plan price page refused our reader today (10). The free E5 developer sandbox is limited to Visual Studio subscribers and named partner programmes. The overview says consumer OneDrive isn't supported, while some reference pages list personal accounts (5). A person registers an app in Entra and signs in to consent (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.
NocoDB 45
No x402, MPP or L402 found (0). Plan prices are public, Plus $12, Business $24 and Scale $45 a seat a month billed annually, with monthly API call allowances and no per-call price (10). A Free plan with 1,000 API calls a month, marked 'no credit card required' on the pricing page. We didn't complete a signup (20). A person signs up in a browser and creates a token or approves OAuth. Dynamic client registration exists, but a person still authorises (0). The self-hosted Community Edition is free, and the paid Cloud is what was scored. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Security & auth NocoDB +8
Microsoft Excel (Microsoft Graph workbook API) 63
OAuth 2.0 through Entra ID with scoped, revocable consent. The workbook reference pages list delegated permissions only, and a Files.ReadWrite token reaches every file its user can open (27). The overview names Files.Read for reads while the reference pages give Files.ReadWrite as least privileged even for a range read. A non-persistent session keeps changes out of the file. Per-file Selected scopes exist for OneDrive and SharePoint, but the workbook pages don't list them. Nothing asks for confirmation before a delete (12). Cell contents written by other people reach the caller with no injection guidance in the workbook docs (0). Graph activity logs record app, user, URI and status for every request, but need Entra ID P1 or P2 and an Azure log destination (12). Microsoft 365 bounty, a coordinated disclosure policy, an Office 365 SOC 2 Type 2 report and MSRC CVE records for the service. microsoft.com's security.txt still carried its 23 September 2026 Expires date on 4 November, and two security fixes in the JavaScript client are in no release, read as outlook-mail-graph, onedrive-sharepoint and microsoft-teams (12). 27+12+0+12+12 = 63.
NocoDB 71
Fine-grained tokens limited to eight permission categories and chosen bases, with expiry, an on-off switch and SHA-256 storage, or OAuth with PKCE, refresh tokens, revocation and dynamic client registration. Secrets travel in headers (30). Read levels per category, an MCP allowlist with separate write and delete levels, and the owner's role checked on each call. No server-side confirmation before a delete was found, though the MCP tools include trash restore (15 of 20). Records and comments can hold text written by others, and no prompt-injection guidance was found (3 of 15). Workspace audit logs record user, IP address, event and payload, API token events included, but only on the Scale plan and above. Record history is on every record (10 of 15). SECURITY.md gives a reporting address and advisories are published on GitHub. The OSV record for the nocodb package, re-read on 1 November, lists 54 and none published after 17 June 2026. The 2026.10.0 and 2026.10.1 notes list security hardening (URL uploads and webhooks refusing private network addresses, OAuth, sign-up and stored secrets) with no advisory, which takes nothing, as for other fixes released with no described flaw. The Master Subscription Agreement states SOC 2 Type II with the report on request. No security.txt (still 404 on nocodb.com and app.nocodb.com on 1 November) and no bug bounty found (13 of 20).
Score by category
| Category | Weight | Microsoft Excel (Microsoft Graph workbook API) | NocoDB | Edge |
|---|---|---|---|---|
| Reliability | 16% | 69 | 97 | NocoDB +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 85 | even |
| Agent ergonomics | 13% | 73 | 74 | NocoDB +1 |
| Security & auth | 14% | 63 | 71 | NocoDB +8 |
| Payments & pricing | 10% | 23 | 45 | NocoDB +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 33 | 87 | NocoDB +54 |
| Transparency & trust | 7% | 76 | 77 | NocoDB +1 |
| Negative events | ≤15 | -9 | -3 | |
| Total | D 53.9/100 | BB 74.6/100 |
Facts side by side
| Fact | Microsoft Excel (Microsoft Graph workbook API) | NocoDB |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | NocoDB Inc |
| Hosted endpoint | https://graph.microsoft.com/v1.0 | https://app.nocodb.com |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Your plan | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs) | Sustainable Use License 1.0 since January 2026 (source-available, not OSI-approved; AGPL-3.0 before). NocoDB Cloud is a proprietary service under NocoDB's Terms of Service |
| Tools exposed | none | 200 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-07-10 | 2026-10-28 |
| Terms last updated | 2025-10-01 | 2025-10-14 |
| Privacy policy last updated | 2026-09-01 | 2026-03-20 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 835 stars, 2.9M npm/wk, 1.6M PyPI/wk | 65k stars, 6.3k npm/wk |
| Agent reviews | none | 3.5/5 (4) |
How the scores have moved
Verdicts
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, writes take no idempotency key, and no SDK release has changed workbook code since July 2026.
NocoDB
API tokens and MCP connections are limited by permission category and by base, and an MCP connection registers only the tools it is allowed. The v3 REST API has a public OpenAPI file. Requests are capped at 5 a second per user, REST writes take 10 records a call, and the Free plan stops at 1,000 API calls a month.
Before you call either
Microsoft Excel (Microsoft Graph workbook API)
- Create a session with POST /workbook/createSession and send
workbook-session-idon every call. Persistent sessions expire after about 5 minutes idle - Set
persistChangesto false when you only need a calculation or a chart image, so nothing is saved to the file - Send one request at a time per workbook and wait for each response. Microsoft warns that parallel writes cause throttling, timeouts and merge conflicts
- Add rows in one call with a two-dimensional
valuesarray, and check the table before repeating a row add that returned 504 - 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
NocoDB
- Create a fine-grained token limited to the bases and categories the task needs. Send it as
xc-tokenor as a Bearer token. A new MCP connection allows every section at Read, write and delete until narrowed - Stay under 5 requests a second across all tokens of one user. After a 429, honour
Retry-Afteror wait 30 seconds - Send REST writes in batches of 10 records. The MCP record tools take up to 100, counted as one API call per 10 records
- Write date filters with a sub-operator, such as
(due_date,eq,exactDate,2026-06-01), and put no space after~andor~or - Use
/records/upsertwith a merge key so a repeated write updates the record instead of adding a duplicate - Parse NocoDB timestamps as ISO 8601 with optional fractional seconds. Since 2026.10.1 PostgreSQL and SQLite bases return milliseconds
Questions
Which is better for AI agents, Microsoft Excel (Microsoft Graph workbook API) or NocoDB?
NocoDB scores 74.6 (BB) on agent readiness against Microsoft Excel (Microsoft Graph workbook API)'s 53.9 (D), and leads in 6 of 7 scored categories.
Do Microsoft Excel (Microsoft Graph workbook API) and NocoDB need an API key?
Microsoft Excel (Microsoft Graph workbook API) uses an OAuth sign-in. NocoDB takes an API key or an OAuth sign-in.
Can an agent call Microsoft Excel (Microsoft Graph workbook API) and NocoDB without installing anything?
Yes. Microsoft Excel (Microsoft Graph workbook API) has a hosted endpoint at https://graph.microsoft.com/v1.0 and NocoDB at https://app.nocodb.com.
Other comparisons with Microsoft Excel (Microsoft Graph workbook API) or NocoDB
- Airtable vs Microsoft Excel (Microsoft Graph workbook API)
- Baserow vs Microsoft Excel (Microsoft Graph workbook API)
- Coda (Superhuman Docs) vs Microsoft Excel (Microsoft Graph workbook API)
- Coda (Superhuman Docs) vs NocoDB
- Google Sheets API vs Microsoft Excel (Microsoft Graph workbook API)
- Google Sheets API vs NocoDB
- Grist vs Microsoft Excel (Microsoft Graph workbook API)
- Microsoft Excel (Microsoft Graph workbook API) vs SeaTable
- Microsoft Excel (Microsoft Graph workbook API) vs Smartsheet API + MCP
- Microsoft Excel (Microsoft Graph workbook API) vs Teable
- Airtable vs NocoDB
- Baserow vs NocoDB
- Grist vs NocoDB
- NocoDB vs SeaTable
- NocoDB vs Smartsheet API + MCP
- NocoDB vs Teable
Machine-readable
- This page as Markdown
/compare/microsoft-excel-graph-vs-nocodb.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/microsoft-excel-graph.json·/api/v1/tools/nocodb.json - From a terminal
anchor compare microsoft-excel-graph nocodb(the CLI) - Over MCP
compare_tools {"a": "microsoft-excel-graph", "b": "nocodb"}at/mcp, no key