USRCP — User Context Protocol MCP server

USRCP — User Context Protocol

Switch AI tools without starting the conversation over.

You told Claude Desktop your stack on Tuesday. On Wednesday, Cursor doesn't know. Thursday, Codex asks again. Every AI tool you use has its own memory, or none.

USRCP is a local, encrypted SQLite ledger that any MCP-aware tool can read and write. Connect supported tools to the same local profile so they can share your recent work, decisions and preferences. USRCP is an early beta; automatic capture and recall depend on the integration.

Registers with Claude Desktop, Cursor, Continue, Cline, and terminal agents (Claude Code, Codex CLI, Copilot CLI, Aider, OpenCode, Antigravity). Captures structured activity from GitHub, Linear, Obsidian, Claude Code sessions, and Google Calendar — plus an experimental conversation-capture set.

brew install frank-bot07/usrcp/usrcp
usrcp init

<!-- TODO(chad): swap the demo link below for the 30s screencast once recorded — runbook in tasks/32-demo-script.md --> → See it work: the cross-editor demo, or check the protocol path on your own machine in one command — node scripts/cross-client-proof.mjs (uses two synthetic MCP clients and scans raw database cells for test content markers; it does not test actual AI hosts). → Apache 2.0 · 600+ tests · threat model in docs/SECURITY.md

Core and optional features: the structured core uses exact-keyword lookup. Optional usrcp-stream adds semantic recall with a different storage/privacy boundary; see the capability matrix below.

Protocol Stack

┌─────────────────────────────────┐
│         Agent Layer             │  ← ACP (Agent-to-Agent)
├─────────────────────────────────┤
│         Model Layer             │  ← MCP (Model Context Protocol)
├─────────────────────────────────┤
│     >>> USRCP <<<               │  ← Structured User State (THIS PROTOCOL)
├─────────────────────────────────┤
│         User / Client           │
└─────────────────────────────────┘

One human, many AI interfaces

USRCP is the human user's context layer. The launch workflow is live retrieval of a compact brief from one shared ledger. Your next assistant should know the relevant ongoing work, decisions, constraints and next steps.

Discuss your work in one connected tool, then ask another: “What was I just working on?” You should not have to select a project, copy a summary, or repeat the background.

Connected MCP clients can read recent activity across the profile with usrcpgetstate and request a focused live brief with usrcp_handoff. The local MCP server provides startup instructions, but clients must honor them; verify actual behavior with the two-client acceptance test. A shared ledger alone does not prove automatic retrieval.

Capability and privacy boundaries

Shortened. The full README is on GitHub.