
Threadmap Mcp
- Updated April 11, 2026
- Advertflair/threadmap-mcp
Threadmap MCP is an MCP server that visualizes Claude conversation drift and enables one-click forks at inflection points.
About
Threadmap MCP is a developer-focused Model Context Protocol server that helps developers who live inside long Claude conversations see where the thread drifted and branch cleanly from those moments. Instead of scrolling thousands of tokens or copy-pasting half a chat into a new window, you get a visual map with color-coded drift and highlighted inflection points, plus one-click forking when you want to try a different implementation or architecture path without losing the preamble. It ships as the npm identifier threadmap-mcp at version 1.0.0 over stdio, fitting standard Claude Code and Cursor MCP setups. It does not replace your git history or issue tracker; it improves conversation hygiene while you are actively building with an agent. Best when sessions routinely split into parallel experiments; skip it if you only run short, single-shot prompts.
- Color-coded visualization of conversation drift across a thread
- Marks inflection points where the dialogue meaningfully shifted
- One-click forking to explore alternate paths without restarting from scratch
- npm package threadmap-mcp v1.0.0 with stdio MCP transport
- Oriented toward Claude long-running coding and planning sessions
Threadmap Mcp by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add threadmap-mcp -- npx -y threadmap-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | threadmap-mcp |
|---|---|
| Transport | STDIO |
| Auth | None |
| Last updated | April 11, 2026 |
| Repository | Advertflair/threadmap-mcp ↗ |
What it does
Visualize how a long Claude thread drifted and fork from inflection points without losing context.
Who is it for?
Best when you're running deep Claude sessions on features, refactors, or architecture and need visual thread control.
Skip if: Skip if you only use single-turn prompts or want code review and CI integrations instead of chat topology.
What you get
You can see drift and inflection points on the thread and fork new lines of work in one click while staying inside your MCP agent.
- Drift and inflection-point views over active conversations
- Forked conversation branches from chosen inflection points
- Clearer navigation of multi-path agent debugging and design explorations
By the numbers
- Published version 1.0.0; npm identifier threadmap-mcp
- stdio MCP transport
- GitHub source: Advertflair/threadmap-mcp
README.md
🗺️ ThreadMap MCP for Claude
Conversation drift visualization and forking for Claude.
Stop losing your original intent. See exactly where your conversation drifted. Fork from any point and pick up with clean context.
See it in action
Color dots on every message — live drift tracking:

Timeline panel with fork buttons at every inflection point:

Two ways to use ThreadMap
| MCP Server | Chrome Extension | |
|---|---|---|
| Works in | Claude Code (terminal) | claude.ai (browser) |
| Install | claude mcp add threadmap npx threadmap-mcp |
Load unpacked from chrome-extension/ folder |
| What you get | 7 tools — track, timeline, fork, branch | Color dots on every message, timeline panel, one-click fork |
| Best for | Developers building with Claude Code | Anyone using claude.ai daily |
Both are in this repo. Use one or both.
Chrome Extension — Visual dots in claude.ai
The Chrome extension injects ThreadMap directly into the claude.ai interface. No config. Just install and open Claude.
Install (2 minutes)
1. Clone or download this repo
2. Open Chrome → chrome://extensions
3. Enable Developer mode (top right toggle)
4. Click Load unpacked → select the chrome-extension folder
5. Open any Claude conversation — ThreadMap activates automatically
What you see
- Color dot next to every message showing drift % from your original intent
- Sticky bar at the top with live drift status and message count
- ↺ rescan — loads all messages from long previous conversations
- timeline — full conversation map, click any row to jump to that message
- ⑂ fork — opens a new Claude chat with full context pre-loaded in the input
How forking works
- Click ⑂ fork in the timeline or next to any message bubble
- A new claude.ai tab opens automatically
- The full context (origin intent + all messages up to that point) is pasted into the input
- Review and hit Send — Claude picks up from the clean version
Chrome extension files
chrome-extension/
├── manifest.json — Extension config (Manifest v3)
├── content.js — Core drift engine + DOM injection
├── threadmap.css — All injected styles
├── popup.html — Extension popup with color legend
├── icon16.png — Icons
├── icon48.png
└── icon128.png
Heads up: The extension uses Developer mode (load unpacked). A Chrome Web Store version is on the roadmap.
MCP Server — Claude Code integration
The MCP server adds 7 tools to Claude Code for programmatic drift tracking.
Install
claude mcp add threadmap npx threadmap-mcp
Or manually add to ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"threadmap": {
"command": "npx",
"args": ["threadmap-mcp"]
}
}
}
Quick start
threadmap_track(sessionId="myproject", role="user", content="build me a login system with JWT auth")
→ 🔵 Blue — Drift: 0% — Origin intent set
threadmap_track(sessionId="myproject", role="user", content="the refresh token keeps expiring after 30 seconds")
→ 🟠 Orange — Drift: 63% — ⚡ INFLECTION POINT detected
threadmap_timeline(sessionId="myproject")
→ Full color-coded map of all messages with fork instructions
threadmap_fork(sessionId="myproject", messageIndex=6, branchName="jwt-debug")
→ 🌿 Branch created — clean context from messages 1–7
All 7 tools
| Tool | What it does |
|---|---|
threadmap_track |
Track a message, get drift score + color |
threadmap_timeline |
Full color-coded conversation map |
threadmap_fork |
Fork from any message index |
threadmap_branch_context |
Clean context packet for any branch |
threadmap_status |
Quick current drift check |
threadmap_reset |
Archive thread, start fresh |
threadmap_legend |
Show color reference guide |
Color system
| Color | Drift | Meaning |
|---|---|---|
| 🔵 Blue | 0–15% | On track — core intent |
| 🟢 Green | 16–35% | Productive expansion |
| 🟡 Yellow | 36–55% | Adjacent drift |
| 🟠 Orange | 56–72% | Inflection point — meaningful pivot |
| 🔴 Red | 73–88% | Full context break |
| 🟣 Purple | 89–95% | Meta — talking about the conversation |
| ⚪ White | 96–100% | Resolution |
Orange and Red = fork candidates. The conversation has left your original intent behind.
Real-world use cases
Claude Code — architecture integrity Track every message while building. Orange = scope creep. Fork before the drift gets worse. Architecture decisions from the first 10 messages stay clean.
Long previous conversations Click ↺ rescan in the Chrome extension. ThreadMap scrolls to the top, loads all messages, scans every one, then returns you to the bottom — all dots appear.
Team handoffs
Use threadmap_branch_context to extract a clean summary of what was decided. Paste it into a new session — no scrolling through 200 messages.
Why open source?
Non-linear conversation navigation is the missing primitive for AI-native work. Right now Claude conversations are books with no table of contents, no chapters, no bookmarks.
ThreadMap is the table of contents. If this becomes the standard, it travels across Claude, GPT, Gemini, anything. Nobody owns it. Everybody benefits.
Roadmap
- Local embedding model (MiniLM) for richer semantic scoring
- Chrome extension on Chrome Web Store (no developer mode required)
- Cross-session persistence (SQLite mode)
- Visual timeline export (SVG/HTML)
- GPT / Gemini compatibility
Contributing
MIT licensed. See CONTRIBUTING.md.
git clone https://github.com/Advertflair/threadmap-mcp
cd threadmap-mcp
npm install
npm run build
PRs welcome especially for: better drift scoring, Chrome extension improvements, and other AI platform support.
License
MIT — see LICENSE
Built by Advertflair. Open source. Ship it.
Recommended MCP Servers
How it compares
Conversation-map MCP utility, not a codebase indexer or deployment MCP.
FAQ
Who is Threadmap MCP for?
Developers and power users of Claude who run long, branching coding conversations and need clarity on where the dialog diverged.
When should I use Threadmap MCP?
Use it during build-heavy agent work when threads are long enough that drift and parallel explorations are slowing you down.
How do I add Threadmap MCP to my agent?
Install and register the npm threadmap-mcp server with stdio transport in your Claude Code, Cursor, or other MCP client configuration.