What is a context window and why does it limit data analysis?
The context window is how much text a model can hold at once: the conversation, files and tool results together. A large table doesn't fit, and what does fit crowds out everything else. A database keeps the data outside the window, so only the answer to each question has to fit.
Steps
- 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.
- Ask your question. Give your AI this prompt:
Using mcpdata, total revenue by channel in Demo.Orders.
| channel | revenue | orders |
|---|---|---|
| Partner | 643,704,238 | 1,201,830 |
| Store | 1,768,785,224 | 3,301,229 |
| Online | 2,951,801,456 | 5,501,941 |
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
Demo.Orders has 10 million rows: far more than any context window. The query below reads all of them in the database and returns three rows, a few hundred characters, to the assistant. That is the whole trick: move the question to the data, not the data to the question.