Claude Context Sync runs on your own machine — the client starts it, so there is no endpoint to ping. 118 installs a week from npm. Last commit 21 May 2026.
Share context, detect conflicts, and message across parallel Claude Code sessions
Today is the operative word: we check Claude Context Sync every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add claude-context-sync -- npx -y claude-context-sync
{
"mcpServers": {
"claude-context-sync": {
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}
[mcp_servers.claude-context-sync]
command = "npx"
args = ["-y", "claude-context-sync"]
{
"mcpServers": {
"claude-context-sync": {
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}
{
"servers": {
"claude-context-sync": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"claude-context-sync"
]
}
}
}
Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.
Lint, measure, and sync AI context files across Cursor, Claude Code, Copilot.
Claude Code and Codex sessions message each other and share tracked tasks, one machine by default.
Persistent memory for Claude Code. Search, recall, and re-inject context from any session.
Self-hosted session relay. Shared threads across Claude Code, Cowork, and Claude.ai.
Persistent memory for Claude Code and Codex. Search and re-inject context from any session.
Shared memory for coding agents: projects, reusable code, sessions and commits across machines
Cross-session memory for Claude Code — context capture, semantic search, recall
Answers built from our own checks of this server.