Hybrid search for Cowork history: FTS, Spotlight, and semantic vectors
Connect Cowork to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Hybrid search for Cowork history: FTS, Spotlight, and semantic vectors. The cowork mcp server is what makes that connection.
An MCP (Model Context Protocol) server for searching and browsing your Claude conversation history stored in ~/.claude/. Works with both Claude Code and Cowork conversations.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Indexing — The server maintains a SQLite database at ~/.claude/.history-index/conversations.db with: - FTS5 virtual table for fast full-text search -@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: OLLAMA_URL, EMBEDDING_MODEL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the database access 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. Cowork's toolset — Indexing — is a fair guide to whether it matches your workflow. It is maintained by egoughnour; 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 |
|---|---|
| Indexing | The server maintains a SQLite database at ~/.claude/.history-index/conversations.db with: - FTS5 virtual table for fast full-text search - Conversation metadata (session ID, project, timestamps, topic) - Full content for |
{
"mcpServers": {
"cowork-history": {
"command": "uvx",
"args": ["cowork-history"],
"env": {
"OLLAMA_URL": "http://localhost:11434",
"EMBEDDING_MODEL": "nomic-embed-text"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OLLAMA_URL | Endpoint or connection string the server talks to. | Yes |
| EMBEDDING_MODEL | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.