Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Share context, detect conflicts, and message across parallel Claude Code sessions
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"claude-context-sync": {
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}Run this in your terminal
claude mcp add claude-context-sync -- npx -y claude-context-syncPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"claude-context-sync": {
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"claude-context-sync": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
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 6, 2026
The registry name was verified with the GitHub account ybin4548, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
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
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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 –, 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.
In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
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
MIT