Share Claude Code sessions with your team.

It's 1am. Production is down. You've been debugging with Claude for 2 hours and found something crucial. Your teammate has a different theory and wants to help.

Instead of copy-pasting chat history or explaining what you tried, hand off your entire Claude Code session. They see every message, every file change, every debugging step. They pick up exactly where you left off.

# You at 1am
cd /my/project
mcc export
# ✓ Session exported to ./mcc-export.json.gz

# Send mcc-export.json.gz to teammate via Slack/email

# Teammate at 1:02am (saves file in their project folder)
cd /my/project
mcc import
# ✓ Session imported!

claude
/resume
# They now see your full 2-hour debugging session and continue from there

That's it. Export creates a file. Import loads it. No setup, no config, no cloud accounts.

curl -fsSL https://raw.githubusercontent.com/lyledean1/mcc/main/install.sh | bash

This automatically detects your platform and installs the latest release.

cargo install --path .

mcc export              # Export current session → ./mcc-export.json.gz
mcc import              # Import session from ./mcc-export.json.gz
mcc preview <file>      # Preview session details without importing
mcc help                # Show help

Back up all your sessions to Google Cloud Storage:

# One-time setup
mcc config set-bucket gs://your-bucket-name

# Backup all sessions
mcc sync

# Restore on another machine
mcc restore

This is perfect for:

• Syncing sessions across multiple laptops
• Backing up your Claude Code history
• Disaster recovery

Your exported session includes:

• Full conversation history - Every message, question, and response
• All file changes - Every edit Claude made
• Complete context - Git branch, working directory, tool calls
• Session metadata - Who exported, when, from which machine

The session file is compressed and typically small (a few hundred KB for most sessions).

mcc export
# Attach ./mcc-export.json.gz to Slack message

mcc export
# Attach ./mcc-export.json.gz to email

mcc export
cp mcc-export.json.gz /path/to/shared/drive/

Your teammate just needs to save the file in their project directory and run mcc import.

Want to see what's in a session before importing?

mcc preview mcc-export.json.gz
# Session Preview:
#   Version: 1.0.0
#   Exported by: alice@laptop
#   Exported at: 2026-01-02T12:34:56Z
#   Project: /Users/alice/projects/myapp
#   Summary: Fix production database timeout issue
#   Messages: 47
#   Git branch: hotfix/db-timeout

• Both you and your teammate need Claude Code installed
• Both should have the project cloned locally
• Project paths can differ (MCC handles this automatically)

• Export at milestones - After fixing a bug, before switching tasks
• Name your exports - Rename mcc-export.json.gz to db-fix.json.gz before sharing
• Project structure - Should generally match between teammates (same repo)
• Git branches - Session includes branch info, but you can resume on any branch

• Export location: ./mcc-export.json.gz (current directory)
• Session storage: ~/.claude/projects/ (Claude Code's session directory)
• Format: Compressed JSON (gzip)
• Session rewriting: Import automatically rewrites paths to match teammate's environment

MIT