REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Share context, detect conflicts, and message across parallel Claude Code sessions
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"claude-context-sync": {
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}Use Claude Context Sync and tell me what you can do for me, then show me one thing✓ If Claude says it is using Claude Context Sync or shows a Claude Context Sync tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Claude Context Sync yet
Claude Context Sync runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Claude Context Sync
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user claude-context-sync -- npx -y claude-context-syncYou should see Claude Context Sync listed as connected
Use Claude Context Sync and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Claude Context Sync or shows a Claude Context Sync tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Claude Context Sync and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Claude Context Sync or shows a Claude Context Sync tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Claude Context Sync and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Claude Context Sync or shows a Claude Context Sync tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user claude-context-sync -- npx -y claude-context-syncClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"claude-context-sync": {
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"claude-context-sync": {
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"claude-context-sync": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026
The registry name was verified with the GitHub account ybin4548, which owns the repo
Code last changed 6 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 6 months ago, and the latest version (0.4.1) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server that automatically summarizes and shares context across parallel Claude Code sessions.
When you run multiple Claude Code sessions on different tasks, each session is unaware of what the others are doing. claude-context-sync watches your session logs, generates structured summaries on demand, and provides real-time file conflict detection and cross-session messaging.
npm install -g claude-context-sync
context-sync init
That's it. The next time you open Claude Code, the MCP server starts automatically. The init command also registers a conflict detection hook.
list_sessionsReturns active Claude Code sessions with their current status, task summary, and any file conflicts.
get_session_contextReturns the full structured summary for a specific session. Automatically re-summarizes if stale. Includes conflict information.
Parameters: sessionId (string)
get_all_changesReturns changed files and decisions across all sessions, with optional project filtering.
Parameters: project (string, optional)
send_messageSends a message to another session. Omit targetSessionId to broadcast to all sessions in the same project.
Parameters: fromSessionId (string), message (string), project (string), targetSessionId (string, optional)
get_messagesReturns message history for a session.
Parameters: sessionId (string), unreadOnly (boolean, optional)
resolve_conflictsClears resolved files from the conflict tracking list.
Parameters: sessionId (string), files (string[])
[Always running] Watcher: detects .jsonl changes → sets stale flag (zero cost)
↓ [On tool call] MCP Tool invoked → summarizes only stale sessions ↓ Extractor → Generator (claude -p) → Store → Response
[Always running] Watcher: detects .jsonl changes
↓ FileTracker: parses Write/Edit tool_use events ↓ SymbolResolver: identifies enclosing function/class/type ↓ Writes per-session touched files
[Every message] Hook (UserPromptSubmit): checks for new conflicts ↓ Alerts Claude once per new conflict → Claude notifies user
Session A: send_message → writes to ~/.claude/context-sync/messages/{targetId}/
↓ Session B: Hook detects unread message → injects into AI context ↓ Claude reads and relays to user → marks as read
Single MCP server process — no separate daemon. Claude Code launches it automatically via stdio transport.
src/
├── mcp/server.ts # MCP server + 6 tools ├── watcher/ │ ├── watcher.ts # File watching (chokidar) │ ├── scheduler.ts # Hybrid summarization strategy │ ├── file-tracker.ts # Real-time file edit tracking │ └── symbol-resolver.ts # Pattern-based symbol detection ├── summarizer/ │ ├── extractor.ts # .jsonl parsing + stratified sampling │ └── generator.ts # claude -p invocation ├── messaging/ │ └── messenger.ts # Cross-session message passing ├── store/store.ts # Local summary cache ├── cli.ts # CLI (init + serve + hook registration) └── types.ts # Shared types
| Language | Detected Symbols |
|---|---|
| TypeScript/JavaScript | function, class, interface, type, enum, const |
| Python | def, class |
| Swift | func, class, struct, protocol, enum, extension |
| Go | func, type (struct/interface) |
| Rust | fn, struct, enum, trait, impl |
Unsupported file types fall back to file-level conflict detection.
claude command available)jq (for conflict detection hook)We'd love to hear from you! If you have feature requests, bug reports, or just want to share how you use claude-context-sync:
git clone https://github.com/ybin4548/claude-context-sync.git
cd claude-context-sync npm install npm run build npm test