mccsync-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mccsync-mcp sync my session list across both Claude accounts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
multicc-sync
Two Claude accounts on one Mac, one session list. Sign out of the Claude desktop app
and into another account and every Claude Code session disappears from the sidebar.
Nothing was deleted: transcripts live in ~/.claude/projects and are shared, but the
app keeps a separate list of sessions per account. mccsync makes both accounts list
the same sessions, and keeps them in step afterwards: renames, archives and deletions
made in one account carry over to the other.
It never touches transcripts, never reads tokens, and makes no network calls. Every write is preceded by a backup.
Install
uv tool install multicc-syncPython 3.11 or newer. For the MCP server as well, install multicc-sync[mcp].
Related MCP server: claude-session-sync
Use
Quit the Claude app, then:
mccsyncThat is the whole update. The first run takes the union of both accounts; later runs carry across whatever changed on either side since the previous run, and say so entry by entry.
mccsync -n # show the plan, write nothing
mccsync list # every account and what it lists
mccsync find "case study" # locate a session in any account, with its transcript path
mccsync adopt # list terminal-only sessions in the app (experimental)
mccsync restore # put back the last backupmccsync --help lists the rest, including --keep-deleted and --accounts A,B for
machines with more than two accounts.
For agents, mccsync-mcp is a stdio MCP server with four tools: find_sessions,
list_accounts, sync_sessions and terminal_only_sessions. Register it in Claude
Code with claude mcp add multicc-sync -- mccsync-mcp. The repository carries a
matching skill in skills/session-sync.
The app's session index is not a documented interface. This tool was written against
Claude desktop 1.49585.0 on macOS and checks the directory layout before every run;
if the app changes it, mccsync stops rather than guesses. Windows and Linux paths
are present but untested.
MIT license.
Available Tools
4 toolsfind_sessionsA
Find sessions whose title, previous titles, working directory or id contain query, in any account.
Returns, most recent first, the account, title, cwd, cli session id and the transcript path on disk, so the caller can open the transcript directly even when the session belongs to another account.
Inputs: query (required), limit.
list_accountsB
Every account index on this machine with its session count, which one is signed in, and whether the app is running.
Inputs: no named parameters.
sync_sessionsB
Preview (default) or apply a sync between the two accounts that hold sessions.
accounts names the pair as two uuid prefixes separated by a comma when more than two accounts
exist. Applying is refused while the desktop app runs; the plan is returned either way.
Inputs: accounts, keep_deleted, apply_changes.
terminal_only_sessionsC
Transcripts that only the terminal claude created and no account lists; mccsync adopt can add them.
Inputs: min_kb.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a clearly distinct operation: listing account status, searching sessions, syncing between accounts, and listing orphaned terminal-only transcripts. No two tools overlap in purpose, and the descriptions make the boundaries obvious.
list_accounts, find_sessions, and sync_sessions consistently follow a verb_noun pattern. terminal_only_sessions is a noun-phrase outlier that describes a category rather than an action, creating a minor but noticeable inconsistency.
Four tools is a compact but reasonable surface for a narrow utility focused on inspecting and syncing existing sessions. Each tool earns its place, and there is no redundancy or bloat.
The core workflows of listing accounts, finding sessions, and syncing between accounts are covered. However, terminal_only_sessions surfaces transcripts that must be adopted via an external `mccsync adopt` command, leaving that discovery-to-action path incomplete within the MCP server.
Maintenance
Related MCP Connectors
Sync coding-agent sessions and resume them in any other agent: Claude Code, Codex, Cursor, more.
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Share context and questions between Claude instances — VS Code, claude.ai web, and mobile.
Your AI apps as one team: hand work to Codex or Claude Code on your Mac, with a shared logbook.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceBrowse, search, rename, split, and clean up Claude Code sessions via MCP, Web UI, or VSCode extension.22MIT
- AlicenseNot gradedqualityDmaintenanceSyncs Claude Code sessions between machines with end-to-end encryption using a recovery phrase.MIT
- AlicenseNot gradedqualityDmaintenanceBridges Claude Code terminal sessions with Claude Chat by exposing session logs as tools, enabling seamless context transfer and two-way communication via a cooperative inbox and optional Google Drive sync.127 npm2MIT
- FlicenseAqualityDmaintenanceEnables web ChatGPT to drive durable, sandboxed Claude Code sessions on a local Mac, with controlled read, modify, verify, and recover operations via six session control tools.6-