mcpdata Request an invite

Answers / Comparisons

Spreadsheet vs database for AI analysis: when should I switch?

Recipe verified on Ran on the public demo (read-only)
Short answer

Switch when the spreadsheet stops being the easy option: more rows than it opens comfortably, several files that should be one table, numbers you need the AI to get exactly right, or a report you rebuild every week. You can keep the spreadsheet: sync it, and it becomes a table.

Steps

  1. Connect your assistant to the public demo. It's a read-only instance with 10 million synthetic orders, so you can try this before you have your own. In Claude Code:
    claude mcp add --transport http mcpdata-demo https://demo.mcpdata.org/mcp --header "Authorization: Bearer cdb_live_PkVoldus8qcE-hqffjajNZzQwiA7rTHMoR4RLSAxsCE"

    The key is public on purpose: it can only read the demo's sample data. For Claude Desktop, Cursor and other apps, see Connect your AI.

  2. Ask your question. Give your AI this prompt:
    Using mcpdata, how many customers are there per segment in Demo.Customers?
What your AI does: the tool call it makes for this prompt, and what came back
query(table_name="Demo.Customers", group_by=["segment"], agg=[{"func": "count", "column": "customer_id", "alias": "customers"}], sort=[{"column": "customers", "desc": true}]) → 3 rows
What you should get · the recipe's real result from its last run
segmentcustomers
Consumer140,152
Small Business44,009
Enterprise15,839

Synthetic data: the demo's orders are generated, not real customers.

The assistant needs mcpdata connected (step 1) to run the query.

Why this works

Spreadsheets are great for looking and editing; an AI reasons over them badly once they're big, because it has to read them. A database lets the AI ask instead of read. Syncing a workbook with cdb-localdata turns each sheet into a table, so you don't have to choose.

Related questions