USRCP — User Context Protocol

Name: USRCP — User Context Protocol
Author: frank-bot07

by frank-bot07version 0.2.8i★ –iRuns on your computer

Registry nameio.github.frank-bot07/usrcp

Install

Overview

Description from the maker (original English)

Encrypted local ledger of structured user state, shared across every MCP-aware AI tool.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Accounting, finance & tax
You need to fill in: USRCP_PASSPHRASE

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: USRCP_PASSPHRASE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "usrcp": {
      "command": "npx",
      "args": [
        "-y",
        "usrcp",
        "serve"
      ],
      "env": {
        "USRCP_PASSPHRASE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add usrcp --env USRCP_PASSPHRASE=your-value -- npx -y usrcp serve

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "usrcp": {
      "command": "npx",
      "args": [
        "-y",
        "usrcp",
        "serve"
      ],
      "env": {
        "USRCP_PASSPHRASE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "usrcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "usrcp",
        "serve"
      ],
      "env": {
        "USRCP_PASSPHRASE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

USRCP_PASSPHRASE secret env
Passphrase used to derive the ledger encryption key. Omit it if the passphrase is stored in the OS keychain via `usrcp keychain store`.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account frank-bot07, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Accounting, finance & taxi

More stars than 0% of the other 1732 servers in this category
Published to the registry more recently than 65% of the other 1732 servers in this category
Basic checks equal to or better than 100% of the other 1732 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is USRCP — User Context Protocol safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: USRCP_PASSPHRASE

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.8) reached the registry 22 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Finance Toolkit, SolidInvoice, Korea Tax Calculator

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Finance Toolkit

by JerBouma

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

Computer or cloud★ 5,496MITUpdated today

Install

SolidInvoice

by SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

Runs in the cloud★ 981MITUpdated 8 days ago

Install

Korea Tax Calculator

by UpstageAI

Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.

Runs on your computer★ 97MITUpdated yesterday

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

→ 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 usrcp_get_state 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

Component	Purpose	Boundary
Structured core	Identity, preferences, projects, facts and timeline	Content encrypted at rest; authorized agents receive decrypted context
Live context retrieval	Recent work and compact context for connected agents	Generated on demand from the local ledger; no file transfer required
Optional stream	Capture and semantic recall	Local embedding vectors are plaintext on disk; optional external embedding providers receive content after consent
Optional device relay	Timeline/stream event sync	Ciphertext content with visible metadata; the local client does not synchronize the entire structured profile

The initial beta focuses on people switching Claude Code, Codex and Cursor. Domain restrictions are optional access controls, not a required step in normal conversation. The broader goal remains continuity for the human user across tools. Read context ownership for inspection, correction, provenance, expiry and deletion alternatives.

Alternatives

OpenMemory also targets cross-tool coding context and automatic capture. Zep provides temporal knowledge graphs. These products overlap with parts of USRCP's workflow. USRCP's proposed advantage is a small, inspectable human-context brief backed by a local encrypted ledger, explicit sharing and no required cloud account for the core workflow. Compare current editions and test against your existing project notes; do not assume other products are merely vector storage or always require a particular provider.

Quickstart

Install

npm (recommended) — the usrcp CLI + encrypted ledger:

npm install -g usrcp        # the `usrcp` command + local ledger

…or run without installing:

npx usrcp init

No native build, no compiler, no postinstall — usrcp uses Node's built-in SQLite (node:sqlite), so npm install just works on any npm (including npm 12+, whose allowScripts default blocks native build scripts). Requires Node ≥ 22.13 (Node 24+ recommended).

Homebrew (macOS / Linux) — alternative for the core CLI:

brew install frank-bot07/usrcp/usrcp

The CLI ships with the inline adapters (terminal, mcp-agent, openclaw). Capture adapters install as their own packages, then you configure each with the setup wizard:

# structured-state adapters:

npm install -g usrcp-github # or usrcp-linear, usrcp-obsidian, usrcp-claude-code, usrcp-google-calendar usrcp setup --adapter=github

experimental conversation-capture set:

npm install -g usrcp-slack # or usrcp-discord, usrcp-telegram, usrcp-imessage, usrcp-gmail usrcp setup --adapter=slack

See the Adapters table for the full list (the Chrome extension and VS Code viewer ship separately — see their package READMEs).

From source — for contributing or running unreleased changes:

git clone https://github.com/frank-bot07/usrcp.git

Build the protocol core first — usrcp-local's build compiles it.

cd usrcp/packages/usrcp-core && npm install && npm run build cd ../usrcp-local && npm install && npm run build && npm link

First run

# Interactive init — prompts for passphrase by default

usrcp init

Non-interactive:

usrcp init --passphrase "your secret phrase" # passphrase mode usrcp init --dev # dev mode (key on disk)

Start the server

usrcp serve

In passphrase mode, init offers to store the passphrase in the OS keychain (macOS Keychain / Linux Secret Service); pass --keychain / --no-keychain to decide non-interactively. With a keychain entry present, MCP clients auto-start the server with no plaintext passphrase in any config file. Manage the entry anytime:

usrcp keychain store    # add/replace (verifies the passphrase unlocks this ledger first)

usrcp keychain status # show backend + whether an entry exists usrcp keychain clear # remove it

Prefer no keychain? The env var path still works:

USRCP_PASSPHRASE="your secret phrase" usrcp serve

init creates ~/.usrcp/users/ / with an encrypted SQLite ledger and writes the MCP server entry to Claude Desktop's config:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Single-user is the default and what every shared-machine consideration in the rest of this README assumes. If two people use the same OS account (or you run multiple identities side by side), see Multiple users on one machine below — each user gets an independent ledger and passphrase under a --user= slug.

Adding capture adapters

Adapters watch a source (a GitHub org, an Obsidian vault, a Linear workspace, etc.) and append the activity you authored into the same ledger your local MCP server reads from. Install the adapter's package, then run the setup wizard to configure it:

npm install -g usrcp-linear          # install the adapter you want

usrcp setup --adapter=linear # configure it (validates credentials, picks scope)

or, to browse what's installed:

usrcp setup # interactive picker

See the Adapters tables below for the full list.

Multiple users on one machine

usrcp init --user=frank

usrcp init --user=jess usrcp serve --user=frank # or rely on --user in the registered MCP entry usrcp users # list available slugs

Each user gets an independent ledger, passphrase, and MCP server entry.

Passphrase mode and terminal agents

If you initialized USRCP in passphrase mode (usrcp init with the default), the MCP server needs the passphrase to decrypt the ledger. The terminal-adapter register() writes only command + args to each agent's config — it never bakes the passphrase in.

Recommended: the OS keychain. One command covers every agent — shell-launched and GUI alike — with nothing in plaintext on disk:

usrcp keychain store

The server checks USRCP_PASSPHRASE, then --passphrase, then the keychain, so existing setups keep working unchanged. (Windows: keychain support isn't wired up yet — use the env-var paths below.)

Env-var alternatives, if you'd rather not use the keychain:

Shell-launched agents (claude-code, codex, copilot-cli, aider, opencode) — add to ~/.zshrc / ~/.bashrc and restart your shell:

  export USRCP_PASSPHRASE="your secret phrase"

GUI/IDE-launched agents (cursor, cline, continue, antigravity) do not inherit shell environment. Either add an env block under the usrcp server entry in the agent's config file (JSON for Cursor/Cline/Continue, TOML for Codex), or set a system-wide GUI env on macOS with launchctl setenv USRCP_PASSPHRASE "..." (persists until reboot; use a ~/Library/LaunchAgents/ plist for permanence).

Treat any config file you bake the passphrase into as a secret — it sits in plaintext on disk and is the weakest link in an otherwise-encrypted setup. This is exactly what usrcp keychain store exists to avoid.

The wizard prints this same guidance after registration, so you can also re-run usrcp setup or usrcp adapter add terminal --targets= for a reminder.

Capture Adapters

Adapters are independent processes that read from a source and append events to the local ledger via the same encrypted-at-rest pipeline as the MCP server. Each adapter handles its own auth, idempotency, and cursor persistence.

Structured-state adapters

These are the headline adapters: they capture genuinely structured dev/work state — issues, PRs, notes, calendar events, coding-session context — the kind of data USRCP's schema and exact-keyword search are built for.

Adapter	What it captures	Mode	Requirements
`usrcp-github`	PRs you opened / merged / closed, issues you opened, comments + reviews you authored, in optional org allowlist	Capture-only (v0)	GitHub personal access token (`repo` + `read:user` scopes)
`usrcp-linear`	Issues + comments you author in Linear	Capture-only (v0)	Linear personal API key
`usrcp-obsidian`	Notes you create or edit in an Obsidian vault	Capture-only (v0)	A local vault directory
`usrcp-claude-code`	User / assistant turns from your Claude Code CLI sessions, tailed from `~/.claude/projects/ /*.jsonl`	Capture-only (stream)	Claude Code CLI installed; `allowlisted_projects` in `~/.usrcp/claude-code-config.json`

| usrcp-google-calendar | Timed events on your primary calendar that have already ended | Capture-only

Only the beginning is shown; read the rest in the repo

USRCP — User Context Protocol

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Accounting, finance & taxi

Common questions

Alternatives

Finance Toolkit

SolidInvoice

Korea Tax Calculator

README from the maker

USRCP — User Context Protocol

Protocol Stack

One human, many AI interfaces

Capability and privacy boundaries

Alternatives

Quickstart

Install

…or run without installing:

experimental conversation-capture set:

Build the protocol core first — usrcp-local's build compiles it.

First run

Non-interactive:

Start the server

Prefer no keychain? The env var path still works:

Adding capture adapters

or, to browse what's installed:

Multiple users on one machine

Passphrase mode and terminal agents

Capture Adapters

Structured-state adapters