OpenCode History

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

在开始新工作前,通过本地只读的 FTS5 索引搜索你过去的 OpenCode 对话历史——无需网络调用。

一句话选型结论

按资料字段整理

OpenCode History 属于文档知识类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
uvx opencode-history-mcp --build-index

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
OpenCode History当前 未标注 stdio · 本地进程 本地部署 有 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

9.0 KB
来自项目仓库与上游目录的原文,未做删改

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.

If this saves you from re-diagnosing the same bug twice, consider dropping a ⭐ — it helps other OpenCode users find it too.

Why

If you use OpenCode 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 than
  scanning JSON blobs on every query.
- **Auto-sync on startup**, TTL-cached (5 min): if OpenCode wrote new
  sessions since the last check, the index catches up incrementally
  before serving results.
- **Privacy is structural, not a policy**: the index lives next to
  OpenCode's own DB, on your machine, under your OS user. There is no
  hosted/shared version of this server — everyone runs their own,
  against their own history.

## Quickstart

### 1. Build the index (first run)```bash
uvx opencode-history-mcp --build-index

This reads your local opencode.db and builds opencode-history.db
next to it. Takes a few seconds per thousand sessions.

2. Add it to your MCP client

Hermes Agent```bash
hermes mcp add history \
--command uvx \
--args opencode-history-mcp


Or in `~/.hermes/config.yaml`:```yaml
mcp_servers:
  history:
    command: uvx
    args:
      - opencode-history-mcp
    enabled: true

OpenCode

In ~/.config/opencode/opencode.jsonc (global) or .opencode/opencode.jsonc
(project):```jsonc
{
"mcp": {
"history": {
"type": "local",
"command": ["uvx", "opencode-history-mcp"],
"enabled": true
}
}
}


Claude Desktop

In `claude_desktop_config.json`:```json
{
  "mcpServers": {
    "opencode-history": {
      "command": "uvx",
      "args": ["opencode-history-mcp"]
    }
  }
}

Cursor / other MCP clients

Any client that supports local stdio MCP servers works the same way —
point it at:```
command: uvx
args: ["opencode-history-mcp"]


### 3. Keep the index fresh (optional)

The server auto-syncs on startup (checked every 5 minutes per session).
For a fully up-to-date index without waiting on that check, run:```bash
uvx opencode-history-mcp --sync-index

You can schedule this with cron/launchd if you want the index always
warm ahead of time.

Tools

Tool Purpose
search_history Full-text search (FTS5) over user prompts and assistant responses. Ranked by relevance + recency + activity.
find_related_work Higher-precision match on session titles and original task descriptions. Best first call for "have we done this before?"
find_sessions_by_file Find every session that modified or mentioned a specific file.
list_sessions Browse sessions in a directory, sorted by date/messages/cost/tokens.
get_session_detail Full metadata for one session: task, files touched, cost, tokens, sub-agent count.
get_session_messages Read the actual paginated message history of a session.
get_stats Aggregate stats: session/message counts, cost, time range, activity distribution.

All tools accept an optional directory parameter to scope results to
one project. Recommended pattern: search scoped to the current
project first; if nothing relevant comes back, retry without
directory for a global search — related work sometimes lives in a
sibling project.

Cross-platform paths

The server resolves OpenCode's data directory the same way OpenCode
itself does (its xdg-basedir-based resolution — see
packages/core/src/global.ts
in the OpenCode source):

Platform Default path Notes
Linux $XDG_DATA_HOME/opencode → falls back to ~/.local/share/opencode Standard XDG Base Directory behavior.
macOS ~/.local/share/opencode ⚠️ Not ~/Library/Application Support/opencode. OpenCode has no macOS-specific branch in its path resolution — it uses the same XDG-style path as Linux. This trips people up who assume Apple conventions apply.
Windows %LOCALAPPDATA%\opencode Falls back to %USERPROFILE%\AppData\Local\opencode if the env var is unset.
WSL (WSL2/WSL1) Same as Linux — ~/.local/share/opencode WSL runs a real Linux kernel, so sys.platform reports "linux" and the Linux path applies automatically. This is only correct if OpenCode itself runs inside WSL.

The WSL + Windows-side-OpenCode edge case

If you installed OpenCode on Windows natively (not inside WSL) but
run your MCP client or terminal inside WSL, the database lives on
the Windows filesystem, which WSL mounts under /mnt/c/.... The
automatic Linux-path resolution will look in the wrong place (your
WSL home directory, not the Windows one) and won't find it.

Fix: point the server explicitly at the mounted Windows path via the
OPENCODE_DATA_DIR environment variable:```bash
export OPENCODE_DATA_DIR="/mnt/c/Users/<your-windows-username>/AppData/Local/opencode"


Or set it in your MCP client&#x27;s `env` config for this server, e.g. for
Hermes:```yaml
mcp_servers:
  history:
    command: uvx
    args:
      - opencode-history-mcp
    env:
      OPENCODE_DATA_DIR: /mnt/c/Users/yourname/AppData/Local/opencode
    enabled: true

Any other custom setup

OPENCODE_DATA_DIR always wins over auto-detection, on every platform
— use it whenever OpenCode's data lives somewhere non-standard (custom
XDG_DATA_HOME, a container, a synced/mounted drive, etc).

Teaching your agent to use this automatically

Having the tools available isn't enough — agents default to exploring
files directly unless told otherwise. Add this to your project's
AGENTS.md (OpenCode) or CLAUDE.md (Claude Code) to make history
search a mandatory first step:```markdown

Check history before starting work

Before exploring files or writing code for any task that touches an
existing module, file, or bug, call the history search tools first:

  1. find_related_work(query=&quot;&lt;short description of the task&gt;&quot;) —
    has this exact task been worked on before?
  2. If the task names a specific file, also call
    find_sessions_by_file(file_path=&quot;...&quot;).
  3. If step 1 returns nothing relevant, broaden with
    search_history(query=&quot;...&quot;) (full-text, no directory scope).

Only start exploring the codebase directly if history search comes up
empty. If a relevant past session is found, read it with
get_session_detail / get_session_messages before proceeding —
don't repeat work or re-diagnose an issue that was already solved.


This is a strong nudge, not a hard constraint — the agent can still
decide history search isn&#x27;t relevant for a truly new task. The goal is
making &quot;check first&quot; the default reflex instead of an afterthought.

## Development```bash
git clone https://github.com/singleflo/opencode-history-mcp.git
cd opencode-history-mcp
uv venv
uv pip install -e .

# Build the index against your own OpenCode history
python -m opencode_history_mcp.build_index --full

# Run the server directly (stdio)
python -m opencode_history_mcp.server

# Inspect with the FastMCP dev tools
fastmcp dev -m opencode_history_mcp.server

See docs/design.md for the full design rationale
(ranking formula, schema decisions, sync algorithm).

Contributing

Issues and PRs welcome. If you hit a platform-specific path issue,
please include your OS, OPENCODE_DATA_DIR (if set), and the actual
location of your opencode.db — that's the fastest way to fix an edge
case in the resolution logic.

License

MIT — see LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
OpenCode History 怎么安装?

在客户端按下面的安装命令接入:uvx opencode-history-mcp --build-index。装完在客户端配置里引用同一个包或端点。

OpenCode History 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

OpenCode History 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

OpenCode History 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

OpenCode History 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

OpenCode History 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

OpenCode History 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

OpenCode History 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。