timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Search your Google, Telegram, Spotify and Instagram exports locally. Fully offline.
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 9/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 3/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Backstory: search your data exports locally。按照 https://mcp.popnx.com/i/magna-nz-backstory.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Backstory: search your data exports locally,按顺序:1) 2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "backstory": { "command": "dnx", "args": [ "Backstory", "--yes", "serve" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Backstory: search your data exports locally 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
SettingsDeveloperEdit Config
{
"mcpServers": {
"backstory": {
"command": "dnx",
"args": [
"Backstory",
"--yes",
"serve"
]
}
}
}用 Backstory: search your data exports locally 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Backstory: search your data exports locally,或回答中出现 Backstory: search your data exports locally 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Backstory: search your data exports locally
Backstory: search your data exports locally 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
可连接 Claude Code,但需要先准备
不需要密钥,不用安装程序
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Backstory: search your data exports locally,按顺序:1) 2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user backstory -- dnx Backstory --yes serve 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Backstory: search your data exports locally 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user backstory -- dnx Backstory --yes serve应能看到 Backstory: search your data exports locally 在列表中并显示已连接
用 Backstory: search your data exports locally 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Backstory: search your data exports locally,或回答中出现 Backstory: search your data exports locally 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
不需要密钥,不用安装程序
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Backstory: search your data exports locally,按顺序:1) 2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "backstory": { "command": "dnx", "args": [ "Backstory", "--yes", "serve" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Backstory: search your data exports locally 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
用 Backstory: search your data exports locally 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Backstory: search your data exports locally,或回答中出现 Backstory: search your data exports locally 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
不需要密钥,不用安装程序
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Backstory: search your data exports locally,按顺序:1) 2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "backstory": { "type": "stdio", "command": "dnx", "args": [ "Backstory", "--yes", "serve" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Backstory: search your data exports locally 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
用 Backstory: search your data exports locally 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Backstory: search your data exports locally,或回答中出现 Backstory: search your data exports locally 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user backstory -- dnx Backstory --yes serveClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"backstory": {
"command": "dnx",
"args": [
"Backstory",
"--yes",
"serve"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"backstory": {
"command": "dnx",
"args": [
"Backstory",
"--yes",
"serve"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"backstory": {
"type": "stdio",
"command": "dnx",
"args": [
"Backstory",
"--yes",
"serve"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 magna-nz 验证,该账户拥有此仓库
代码最后更新于5个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/magna-nz-backstory)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于5个月前,最新版本(1.1.0)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 .NET。
同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 Backstory: search your data exports locally | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Search all your data exports in one place. It runs entirely on your own computer, and nothing ever leaves your PC.
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.
| Source | What it imports | How to export it |
|---|---|---|
| Google Takeout | Search history, YouTube history, saved places, location history | backstory fetch google |
| Telegram | Messages, contacts | backstory fetch telegram |
| Spotify | Listening history, podcasts, searches | backstory fetch spotify |
| Direct messages, posts, comments, searches | backstory fetch instagram |
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 result.json"]:::src GT["Google Takeout JSON / CSV"]:::src
TG --> AD GT --> AD
AD["Adapters parse and normalize "]:::ingest NR["Normalizer events and entities "]:::ingest ER["Entity resolution link people and places "]:::ingest AD --> NR --> ER
ER --> FTS[("SQLite + FTS5 timeline, keyword")]:::store ER --> VEC[("Vector index meaning")]:::store
FTS --> HQ VEC --> HQ HQ["Search keyword + meaning "]:::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.
| Command | What it does | |||
|---|---|---|---|---|
| `fetch google\ | telegram\ | spotify\ | instagram` | Show how to export your data, and open the page |
watch [--dir ] | Import exports automatically as they download to ~/Downloads | |||
import | Import an export (file, folder, or Takeout zip) | |||
search " " | Search the timeline. Filters: --from --to --source --limit | |||
timeline | List events in time order, with the same filters | |||
entity " " | Look up a person or place | |||
stats | Counts by source and type, and the embedder in use | |||
serve | Run the MCP server | |||
model fetch | Download the semantic search model (optional, one time) | |||
eval | Run the benchmark |
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.
| Embedder | Data parsed | Right answer in top 5 |
|---|---|---|
| Hashing (default) | 100% | 87.5% |
| ONNX MiniLM | 100% | 100% |
| Tool | What it returns |
|---|---|
search_timeline | Ranked events for a natural-language query |
get_events | Full event records by id, including a pointer to the source |
lookup_entity | A person or place by name |
summarize_period | Every event in a date range, for the agent to summarize |
list_sources | The sources imported and how many events each has |
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.