Backstory: search your data exports locally MCP server
io.github.magna-nz/backstory·v1.1.0·5 starsSearch your Google, Telegram, Spotify and Instagram exports locally. Fully offline.
5 stars
Reviews
Write oneNobody has reviewed Backstory: search your data exports locally yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Backstory: search your data exports locally tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 89 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Backstory: search your data exports locally compares
Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 65% of 3,471 Web search servers
- GitHub stars
- 5
- more than 80% of 1,788 Web search servers
Install Backstory: search your data exports locally in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Backstory: search your data exports locally repository's README, as published. We do not edit it. Read it on GitHub
Backstory
Search all your data exports in one place. It runs entirely on your own computer, and nothing ever leaves your PC.
<!-- mcp-name: io.github.magna-nz/backstory -->
You can download your data from Google, Telegram, and most other services. The problem is what you get back: a pile of JSON and CSV files that are nearly impossible to read. Backstory pulls those exports into one local database and lets you search across all of them at once. You can search from the command line or connect it to an AI assistant over MCP.
Nothing is sent to the cloud. Your data stays in a SQLite file on your machine. That is the main reason this tool exists, since this is the most personal data you have.
Contents
- What it can do
- Sources
- Quick start
- Use it from an AI agent
- How it works
- Commands
- Search quality
- MCP tools
- Privacy
- License
What it can do
- Import exports from Google, Telegram, Spotify, and Instagram.
- Search everything as one timeline, by meaning or by keyword.
- Match the same person or place across different sources.
- Answer questions from an AI agent, like "when did I last message Sarah about dinner?".
- Show you how to export your data, then import it automatically when it finishes downloading.
- Report a benchmark so you can see how well the search actually works.
Sources
Each source is a small adapter that turns an export into events. Here is what works today and what each one pulls in.
Adding a new source means writing one adapter. Nothing else changes.
Quick start
You need the .NET 10 SDK. It runs on Linux, macOS, and Windows.
Install as a global tool:
dotnet tool install -g BackstoryOr build from source today:
git clone https://github.com/magna-nz/backstory && cd backstory
dotnet build Backstory.slnx -c ReleaseGet your data in. Backstory shows you how to export it, then imports it for you when it lands in your Downloads folder:
backstory fetch google # or: telegram
backstory watchYou can also point it at a file or zip yourself. Takeout zips are unpacked for you, including the multi-part ones:
backstory import ~/Downloads/takeout-20240101.zip
backstory import ~/Downloads/telegram-export/result.jsonThen search:
backstory search "dinner plans with sarah"
backstory search "trip to japan" --from 2023-01-01Use it from an AI agent
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Backstory: search your data exports locally: common questions
- Is Backstory: search your data exports locally MCP server safe?
- Mostly: it is graded B (80/100). Read the Backstory: search your data exports locally safety report
- Does Backstory: search your data exports locally need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Backstory: search your data exports locally maintained?
- The last commit was 129 days ago (2026-06-29). The latest release is v1.1.0.
- What can I use instead of Backstory: search your data exports locally?
- Servers from other publishers that do the same job: HasData Google Scholar MCP server, Google Maps MCP Server and Search1API MCP server.
- How does Backstory: search your data exports locally compare with other Web search MCP servers?
- safety score 80/100 (higher than 65% of 3,471 Web search servers); github stars 5 (more than 80% of 1,788 Web search servers). Full comparison.
Alternatives to Backstory: search your data exports locally
Same job from other publishers: the closest match first, then the best rated.
HasData Google ScholarGoogle Scholar search results, citation counts and citation export formats, as structured JSON.not reviewedGrowingA- Google Maps MCP Server18 Google Maps tools for AI agents — geocode, search, directions, weather, and more.not reviewedEstablishedB
Search1APIMulti-engine web and platform search, news, Google Maps places, page reading, sitemaps, and trends.not reviewedEstablishedA
Chatroost — unofficial Telegram MCP serverUnofficial Telegram MCP server — read, search, reply and react in your own Telegram account.not reviewedEstablishedA- Suede AI Skills MCPRoutes tasks to Suede skills, grades live pages A-F for Google and AI search, and checks copy.not reviewedEstablishedA
