MCP server for reading Claude Code session history from the local filesystem
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":"node804-claude-code-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.
# node804-claude-code-mcp [](https://pypi.org/project/node804-claude-code-mcp/) [](https://pypi.org/project/node804-claude-code-mcp/) [](LICENSE) [](https://github.com/Node804/node804-claude-code-mcp/actions/workflows/ci.yml) MCP server for reading Claude Code session history from the local filesystem. Exposes project and session data to any MCP-compatible client — Claude Cowork, Claude Chat, scheduled agents, or your own tooling. Reads directly from `~/.claude/projects/` — no external dependencies, no network calls, no API keys. --- ## Why this exists Claude Code stores every session as a local JSONL file containing the full conversation: user messages, assistant responses, tool calls, token counts, and timing. That history is rich and detailed, but it's locked inside the CLI with no way to query it from other tools. This server opens it up. ### Use cases **Personal Knowledge Management and daily logging** Claude Code sessions are a detailed record of decisions made, problems solved, and code written. This server lets a Cowork or Chat session pull that raw material into a daily note, work log, or PKM entry automatically — capturing not just *what* changed but the reasoning behind it, without any manual copy-paste. **Cross-session continuity** Starting a new Claude Code session on a project that was last touched weeks ago means re-explaining context from scratch. With this server, a fresh session can search prior conversations for relevant background — design decisions, dead ends already explored, environment quirks — before writing a single line of code. **Standup and progress reporting** `search_claude_sessions` and `get_claude_session_stats` giv…
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.