Search your Google, Telegram, Spotify and Instagram exports locally. Fully offline.
Connect Backstory: Search Your Data Exports Locally to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Search your Google, Telegram, Spotify and Instagram exports locally. Fully offline. The backstory: search your data exports locally mcp server is what makes that connection.
Search all your data exports in one place. It runs entirely on your own computer, and nothing ever leaves your PC.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
timeline — List events in time order, with the same filtersstats — Counts by source and type, and the embedder in useserve — Run the MCP servereval — Run the benchmarksearch_timeline — Ranked events for a natural-language queryget_events — Full event records by id, including a pointer to the sourcelookup_entity — A person or place by namesummarize_period — Every event in a date range, for the agent to summarizelist_sources — The sources imported and how many events each hasSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Backstory: Search Your Data Exports Locally's toolset — timeline, stats, serve and 6 more — is a fair guide to whether it matches your workflow. It is maintained by magna-nz; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| timeline | List events in time order, with the same filters |
| stats | Counts by source and type, and the embedder in use |
| serve | Run the MCP server |
| eval | Run the benchmark |
| 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 |
{
"mcpServers": {
"backstory": { "command": "backstory", "args": ["serve"] }
}
}Configuration as documented by the project. Restart the client after saving.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.