Backlit is in private, invite-only beta, public launch coming soon.

How to get your app's data back out (and query it with Claude)

Saving data is only half the job. Getting it back out and doing something with it is the other half. Here's how to query and export your Backlit app's data straight from Claude through the MCP.


Most advice about app data stops at storing it. But storing is the easy half. The half that actually matters is getting the data back out: answering “how many signups this week?”, exporting the orders, moving new leads into your spreadsheet. If that part is hard, the data may as well not be there. Here’s how Backlit closes the loop.

The quick answer

Your Backlit app’s data is reachable through Backlit’s MCP server, the same connection your assistant uses to deploy. So you get the data back out by asking Claude in plain language: “summarise this week’s form responses,” “export the orders as a CSV,” “add the new signups to my Notion.” Claude reads the app’s data through the MCP and does it. No SQL, no admin dashboard, no export button you had to remember to build.

Why getting data out is usually the painful part

Think about how this normally goes. Your app collects responses. To see them, you either build an admin screen (more app to write and secure), or you wire up a database you then have to query yourself, or you add an export button and download CSVs you open by hand. Every one of those is extra work, and most small apps never get it, so the data just sits there, technically saved and practically stuck.

The reason is that storage and analysis are usually two different tools. The place that holds the data isn’t the place you think in.

How Backlit closes the loop

Backlit’s bet is that the place you already think in is the chat. You built the app there. You deployed it there. So you should be able to interrogate its data there too.

Because the app’s data lives behind Backlit’s MCP, your assistant can reach it the same way it reached in to publish the app. In practice:

  1. Your app saves data as it’s used (shared data, per-user data, or form captures through window.backlit.*).
  2. With Backlit connected, you ask Claude about that data in plain language.
  3. Claude queries it through the MCP and answers, summarises, or hands it back in whatever shape you asked for.

The loop is closed: data goes in through the app, and comes back out through the assistant.

What that looks like

  • “How many people filled in the intake form this week, and what are the common themes?”
  • “Export every order from the last month as a spreadsheet.”
  • “Push any new waitlist signups into my Notion table.”
  • “Which family members haven’t logged a chore today?”

These aren’t reports you built. They’re questions you asked, against data the app was already saving.

Why this is genuinely differentiating

Most hosts hand you a database and wish you luck. The data is there, but using it is a separate project with separate tools. Backlit treats “get the data back out” as part of the product, through the same MCP surface that makes deployment a one-line request. For the kind of person Backlit is for, someone who built an app in a chat and doesn’t want a second career in analytics, that’s the whole difference. It was the part of a live demo that landed hardest: not just that your app saves data, but that you can turn around and ask your assistant about it.

What it isn’t

This is plain-language query and export, not a business-intelligence suite. There are no dashboards to design or pipelines to maintain, on purpose. If you need heavy analytics, scheduled reports, and a warehouse, that’s a different tool. For “tell me what’s in my app’s data and hand me a copy,” the assistant plus the MCP is enough, and it’s right there.

The takeaway

Data you can’t get back out isn’t really yours to use. Backlit makes the way out as simple as the way in: ask Claude, through the MCP, and your app’s data comes back as an answer or an export. If you’re thinking about what your app should store in the first place, start with how to save the data people enter, and see the agent surface for how the MCP connection works.


Built an app with Claude or ChatGPT? Get early access to Backlit and share it in seconds.