Cross-Machine Context Sync
Cross-Machine Context Sync
The Problem
I work on two machines:
- Mac - Primary development, client work
- Z13 - AI experimentation, local LLM hosting
Switching machines meant losing context. I’d start a project on the Mac, switch to Z13, and have to remember where I left off. Manual. Friction.
The Solution
Real-time context synchronization via MCP (Model Context Protocol) server.
Architecture
Mac → shared-context-mcp → Upstash Redis ← shared-context-mcp ← Z13
Components:
- MCP Server (Node.js) - Runs locally on each machine
- Vercel Edge Functions - API layer for context operations
- Upstash Redis - Free-tier cloud state storage (10k commands/day)
Operations
// Set context (from Mac)
set_context("current_focus", "Implementing MCP infrastructure")
// Get context (from Z13)
get_context("current_focus")
// Returns: "Implementing MCP infrastructure"
// List all context
list_context()
// Delete when done
delete_context("current_focus")
Simple key-value store. But the synchronization is instant.
What Makes It Useful
Zero-friction context switching: Set context on Mac before bed. Wake up, switch to Z13, context is there.
AI continuity: Claude on Mac can communicate with Claude on Z13 via shared state.
No git commits needed: Not everything needs version control. Ephemeral state (like “what I’m currently focused on”) lives here.
Optional TTL: Set expiration times on context items. Old context auto-cleans.
Use Cases
Active development:
- Current focus/objectives
- Blockers encountered
- Next steps
- Open questions
Cross-machine coordination:
- “Mac is building Docker image, check status on Z13”
- “Test results uploaded, review on Mac”
AI memory:
- Pattern observations
- Decisions made
- Things to remember
Current Status
Operational. Tested with 6 MCP servers. Context set on Z13 is instantly retrievable. Mac setup pending (will copy template and adjust paths).
The infrastructure works. Now exploring optimal workflow patterns.
Technologies: Model Context Protocol, Node.js, Upstash Redis, Vercel Edge Functions Status: Operational on Z13, Mac setup pending Cost: $0/month (free tier)