Backstory
Search all your data exports in one place. It runs entirely on your own computer, and nothing ever leaves your PC.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
nuget BackstoryClaude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add io.github.magna-nz-backstory -- nuget Backstoryรันในเทอร์มินัล
{ "mcpServers": { "io.github.magna-nz-backstory": { "command": "nuget", "args": [ "Backstory" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิด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.
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.
You need the .NET 10 SDK. It runs on Linux, macOS, and Windows.
Install as a global tool:
dotnet tool install -g Backstory
Or build from source today:
git clone https://github.com/magna-nz/backstory && cd backstory
dotnet build Backstory.slnx -c Release
Get 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 watch
You 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.json
Then search:
backstory search "dinner plans with sarah"
backstory search "trip to japan" --from 2023-01-01
Backstory speaks MCP, so any MCP client (Claude and others) can query your timeline. Start the server:
backstory serve
Register it with one command:
claude mcp add backstory -- backstory serve
Or add it to your MCP config directly:
{
"mcpServers": {
"backstory": { "command": "backstory", "args": ["serve"] }
}
}
Now you can ask the agent things like "what was that ramen place I looked up in Tokyo?" and it searches across both your Google and Telegram data to answer.
Every export format is messy in its own way, so a small adapter handles each one and converts it into the same shape: events on a timeline, plus the people and places they mention. From there everything works the same. Storage is SQLite with a full-text index for keywords and a vector index for meaning. A search runs both and combines the results.
flowchart TD
TG["Telegram<br/>result.json"]:::src
GT["Google Takeout<br/>JSON / CSV"]:::src
TG --> AD
GT --> AD
AD["Adapters<br/><i>parse and normalize</i>"]:::ingest
NR["Normalizer<br/><i>events and entities</i>"]:::ingest
ER["Entity resolution<br/><i>link people and places</i>"]:::ingest
AD --> NR --> ER
ER --> FTS[("SQLite + FTS5<br/>timeline, keyword")]:::store
ER --> VEC[("Vector index<br/>meaning")]:::store
FTS --> HQ
VEC --> HQ
HQ["Search<br/><i>keyword + meaning</i>"]:::query
HQ --> CLI["CLI"]:::iface
HQ --> MCP["MCP server"]:::iface
classDef src fill:#FAECE7,stroke:#993C1D,color:#4A1B0C;
classDef ingest fill:#EEEDFE,stroke:#534AB7,color:#26215C;
classDef store fill:#E1F5EE,stroke:#0F6E56,color:#04342C;
classDef query fill:#E1F5EE,stroke:#0F6E56,color:#04342C;
classDef iface fill:#F1EFE8,stroke:#5F5E5A,color:#2C2C2A;
There is a full technical writeup at magna-nz.github.io/backstory and in SPEC.md.
The database lives at $BACKSTORY_DB, or ~/.backstory/backstory.db by default.
There are two ways to turn text into vectors, and you can switch between them:
backstory model fetch once (about 90 MB) and Backstory uses it automatically. This is what lets a search for "japan vacation" find a message about a "flight to Tokyo".You can measure the difference yourself with backstory eval. It loads sample data and reports two numbers: how much of the data was parsed, and how often the right event shows up in the top five search results.
Everything runs locally and there is no telemetry. The only time Backstory touches the network is when you run backstory model fetch to download the search model, and that step is optional. Your data never leaves your machine. The .gitignore is set up so a database or an export can't be committed by accident.
MIT. See LICENSE. Built on the ModelContextProtocol SDK, ONNX Runtime, and all-MiniLM-L6-v2.
Search your Google, Telegram, Spotify and Instagram exports locally. Fully offline.
{ "mcpServers": { "io.github.magna-nz-backstory": { "command": "nuget", "args": [ "Backstory" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Backstory: Search Your Data Exports Locally ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Search your Google, Telegram, Spotify and Instagram exports locally. Fully offline.