MCP server for searching your local OpenCode conversation history
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"opencode-history-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# OpenCode History MCP A local MCP (Model Context Protocol) server that lets AI coding agents search your **past OpenCode conversations** — before they start exploring files or re-doing work you already did. Everything runs on your machine: it reads OpenCode's own SQLite database and builds a private full-text search index next to it. No network calls, no external services, **no data ever leaves your computer**. [](https://www.python.org/) [](LICENSE) [](https://modelcontextprotocol.io) ## Why If you use [OpenCode](https://opencode.ai) daily across many projects, you build up thousands of past sessions — bug fixes, feature work, diagnostics — sitting untapped in `opencode.db`. When you start a new session on the same module or file, your agent has no idea any of that happened. It re-explores from scratch, or worse, repeats a mistake you already fixed three weeks ago. This server exposes that history as MCP tools any agent can call: *"has this file been touched before? what did we conclude last time? what related work exists in this project?"* ## How it works ``` OpenCode's own DB (read-only) Our derived index (read-write) ┌─────────────────────────┐ ┌──────────────────────────┐ │ opencode.db │ builds → │ opencode-history.db │ │ - session / message /part│ │ - sessions (denormalized) │ │ - JSON blobs per row │ │ - search_idx (FTS5) │ └─────────────────────────┘ │ - session_files (index) │ └──────────────────────────┘ ``` - **Source DB stays untouched.** We open it `mode=ro` (read-only, WAL-aware) and never write to it. - **A separate FTS5 index** holds denormalized session metadata + full-text search over user/assistant text — orders of magnitude faster t…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.