usrkey.dev / guides / mcp

Your agent, briefed in 10 minutes.

From an empty folder to an agent that already knows the user — over MCP, with nothing invented: every step below was run before it was written down.

1 · Have some pages

A USRKey is a directory of markdown pages, canonically ~/.usrkey/. Get one either way:

The easy way: make a key at usrkey.com (60 seconds) and use "Save to a folder" on the final screen, picking ~/.usrkey. By hand: see the by-hand guide — it's just files.

2 · Install the connector

$ npm i -g https://usrkey.dev/usrkey-connector-0.2.0.tgz

Node 18+. Three files, ~3 kB, MIT — the tarball is the entire source; read it first.

3 · Wire it into your client

Claude Desktop — add one entry to the config and restart:

// ~/Library/Application Support/Claude/claude_desktop_config.json
{ "mcpServers": { "usrkey": { "command": "usrkey-connector" } } }

Cursor / Cline / Continue — add an MCP server with command usrkey-connector in each tool's MCP settings. To point at a non-default folder, set USRKEY_DIR=/path/to/pages in the server's environment.

4 · What your agent receives

Your agent calls one tool, get_my_context, and gets one string — verbatim, for a two-page key:

Context the user chose to share about themselves. Use it to work
with them as they are — don't re-ask what's already here.

# identity

## One paragraph

Frank — runs a woodworking business in Ohio. Wants tools to write
in plain, direct language.

---
# now

## Current focus

Launching the new product line this month.

Want one page instead of everything? Each page is also an MCP resource — usrkey://identity, usrkey://now, and so on.

5 · Behave

Three rules make you a good citizen of someone else's context: don't keep it (read fresh each session, no syncing, no training), don't backfill it (a missing page is a choice), and don't touch boundaries.md unless explicitly granted. The full rules live on the format page.

Done? Run your page through the validator, grab the badge, and get listed as an adopter.