MCP.so
Sign In
C

Claude Context Sync

@ybin4548

Repository

About Claude Context Sync

Share context, detect file conflicts, and send messages across parallel Claude Code sessions

#claude-code#mcp#context-sharing#conflict-detection#parallel-sessions#messaging

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "claude-context-sync": {
      "command": "npx",
      "args": [
        "-y",
        "claude-context-sync",
        "serve"
      ]
    }
  }
}

Tools

6

활성 Claude Code 세션 목록과 요약 상태를 반환합니다

특정 세션의 구조화된 요약을 반환합니다. 낙후된 경우 자동으로 재요약합니다.

모든 세션의 변경 파일과 결정사항을 통합하여 반환합니다

충돌이 해결된 파일을 추적 목록에서 제거합니다

다른 세션에 메시지를 전달합니다. targetSessionId 생략 시 같은 프로젝트의 모든 세션에 브로드캐스트합니다.

세션의 수신 메시지 이력을 조회합니다

Overview

What is Claude Context Sync?

Claude Context Sync is an MCP server that automatically summarizes and shares context across parallel Claude Code sessions. It watches session logs, generates structured summaries on demand, and provides real-time file conflict detection and cross-session messaging for developers running multiple Claude Code sessions simultaneously.

How to use Claude Context Sync?

Install globally with npm install -g claude-context-sync then run context-sync init. The MCP server starts automatically the next time you open Claude Code, and the init command registers a conflict detection hook. Four tools are available: list_sessions, get_session_context, get_all_changes, send_message, get_messages, and resolve_conflicts.

Key features of Claude Context Sync

  • Session context sharing across parallel Claude Code sessions
  • Real-time file conflict detection with symbol-level accuracy
  • Cross-session messaging between terminals without switching
  • Lazy evaluation with zero cost when tools aren't called
  • Auto-cleanup of tracked data when sessions end
  • Symbol-level detection for TypeScript, Python, Swift, Go, and Rust

Use cases of Claude Context Sync

  • Working on multiple features simultaneously with full context awareness
  • Preventing file conflicts when multiple sessions edit the same codebase
  • Sending messages between sessions without leaving the terminal
  • Getting a bird's-eye view of all active Claude Code sessions and their changes

FAQ from Claude Context Sync

How does Claude Context Sync share context between sessions?

It watches your session logs for changes, marks sessions as stale at zero cost, and when a tool is called it summarizes only stale sessions by parsing .jsonl files and generating structured summaries using claude -p.

What languages are supported for symbol-level conflict detection?

TypeScript/JavaScript, Python, Swift, Go, and Rust. Unsupported file types fall back to file-level conflict detection only.

Does Claude Context Sync require a separate daemon process?

No. It runs as a single MCP server process that Claude Code launches automatically via stdio transport with no separate daemon.

Where is session data stored and when is it cleaned up?

Data is stored locally in ~/.claude/context-sync/ and tracked data is automatically removed when sessions end.

What are the runtime requirements?

Node.js 20+, the Claude Code CLI (claude command available), and jq for the conflict detection hook.

Frequently asked questions

How does Claude Context Sync share context between sessions?

It watches your session logs for changes, marks sessions as stale at zero cost, and when a tool is called it summarizes only stale sessions by parsing `.jsonl` files and generating structured summaries using `claude -p`.

What languages are supported for symbol-level conflict detection?

TypeScript/JavaScript, Python, Swift, Go, and Rust. Unsupported file types fall back to file-level conflict detection only.

Does Claude Context Sync require a separate daemon process?

No. It runs as a single MCP server process that Claude Code launches automatically via stdio transport with no separate daemon.

Where is session data stored and when is it cleaned up?

Data is stored locally in `~/.claude/context-sync/` and tracked data is automatically removed when sessions end.

What are the runtime requirements?

Node.js 20+, the Claude Code CLI (`claude` command available), and `jq` for the conflict detection hook.

Comments

Basic information

Category

AI & Agents

Transports

stdio

Author

ybin4548

Submitted by

ybin4548

More AI & Agents MCP servers

Competitor Tracker & Co.

Competitor Tracker & Co.

Competitor Tracker & Co. watches your competitors' websites and tells you what changed. Every week it crawls their pricing, product, messaging and corporate pages, detects the changes that matter, and files a tagged, ran

scvd.store

seancrecord

The trust layer of the x402 economy. Free conformance checking for any issuer's x402 signed offers and receipts. Settlement attestation on Base and Solana. Weekly signed, Bitcoin-anchored ecosystem corpus.

2

Mcp Agent

lastmile-ai

Build effective agents using Model Context Protocol and simple workflow patterns

8.4K
F

fhirHydrant

faulkj

Open-source Node.js FHIR MCP server with SMART Backend Services, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, and terminology lookup.

14

🛡️ A.I.G（AI-Infra-Guard）

Tencent

A full-stack AI Red Teaming platform securing AI ecosystems via OpenClaw Security Scan, Agent Scan, Skills Scan, MCP scan, AI Infra scan and LLM jailbreak evaluation.

4.1K