People Context

people-context

English | 简体中文

Your agent already remembers your codebase. Now it can remember your people.

people-context is a local-first MCP server and CLI that gives AI agents durable memory about the people in your life: who someone is, how you know them, what you last agreed, and how they like to be talked to. One SQLite file on your machine. No account, no cloud, no network calls.

Why

Ask an assistant "how should I approach Priya about the reporting delay?" and it has nothing: it does not know which Priya, that she is your counterpart at a partner org, that you agreed a new deadline last week, or that she prefers a short email over a call. That knowledge lives in your head, your inbox, and a notes file the agent cannot see.

people-context keeps it in one place the agent can query through narrow tools:

• Who is this? Explainable name resolution over names, nicknames, aliases, and handles. Two Priyas come back as two candidates with a match reason, never a silent guess.
• What do I know? Relationships, organisations and roles, durable facts, concise interaction summaries, traits, reminders, and a per-person timeline, each disclosed only as far as the request needs.
• How do I talk to them? Communication guidance grounded in recorded traits, past friction, open follow-ups, and your own written philosophy.
• Who has gone quiet? Stale-relationship and upcoming-date reports over what is already stored.
• Get data in safely. Email, mbox, vCard, calendar, LinkedIn, Outlook, and WhatsApp exports are staged as reviewable candidates. You approve what gets recorded; raw source content is never kept.

It is opinionated about trust: writes are audited, forget is a real delete, sensitive records sit behind an operator-only gate that a prompt cannot open, and ordinary commands never touch the network.

Demo

A packaged fictional dataset is the fastest way to see identity resolution, graph traversal, and bounded context without touching real data:

uvx --from people-context pctx demo --reset

The demo always writes its own dedicated database at {XDG_DATA_HOME or ~/.local/share}/people-context/demo.db. It ignores --db, PEOPLE_CONTEXT_DB, the config file, and --reset replaces only that file plus its -wal/-shm companions, so a real database is never read or modified. Seeding writes audited fictional people, handles, affiliations, facts, interactions, and a connected relationship graph, then prints the path-targeted server command and concrete tool calls that use the ids it just created:

Demo database: /home/you/.local/share/people-context/demo.db

Start MCP server: people-context-mcp --db /home/you/.local/share/people-context/demo.db resolve_person {"query": "Amina Hassan"} get_relationship_graph {"person_id": " ", "depth": 2} find_connection {"person_a": " ", "person_b": " "}

Person ids are generated per seed, so the printed values differ from the placeholders above. Start the printed server command in an MCP client and run the printed calls verbatim. See docs/cli.md.

Quick start

Requires Python 3.11+ and uv. Pick your client; each is one step.

Claude Code

claude plugin marketplace add JinyangWang27/people-context

claude plugin install people-context@people-context-plugins

Restart Claude Code or run /reload-plugins. You get the server plus /people-context:who, /people-context:remember, and /people-context:reminders. Details: docs/claude-code-plugin.md.

Claude Desktop

Download people-context.mcpb from the latest release and open it. Claude Desktop installs the pinned release with its own uv runtime. Details: docs/desktop-and-editors.md.

Codex

codex plugin marketplace add JinyangWang27/people-context

codex plugin add people-context@people-context-plugins

Start a new Codex session. Details: docs/codex-plugin.md.

Cursor, Windsurf, VS Code, or any MCP client

Add the stdio server to your client's MCP config (.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, .vscode/mcp.json, ...):

{

"mcpServers": { "people-context": { "command": "uvx", "args": ["--from", "people-context", "people-context"] } } }

Or let the CLI write it: uvx --from people-context pctx setup cursor (also windsurf, vscode, claude-desktop; add --dry-run to preview). VS Code uses a servers key with "type": "stdio". Per-editor snippets: docs/desktop-and-editors.md.

OpenClaw

openclaw plugins install clawhub:openclaw-plugin-people-context

The native plugin talks to the opt-in loopback HTTP server. Details: docs/openclaw-plugin.md.

CLI only

uv tool install people-context

pctx init # seed your own record, optionally import a vCard, then connect a client pctx --help

people-context and people-context-mcp are the server commands; pctx is the human-operated CLI.

Then try, in your agent:

Who is Amina?

Remember that Amina from Open City Lab prefers short emails and hates surprise calls.

What should I know before my meeting with Daniel tomorrow?

The second one is a single remember tool call: the name is resolved, the person is created only if nobody matches, and the affiliation and preference are recorded in one audited transaction. Ambiguous names come back as candidates, never a guess.

Or, without an agent: pctx remember "Amina Hassan" "prefers short emails" --org "Open City Lab" and pctx brief "Amina Hassan". Five worked scenarios live in docs/use-cases.

Review and edit in your browser

Prefer a table to a terminal? pctx browse --open opens a local page over the same database:

• browse people and open one person's brief;
• add, correct, or remove a person's aliases and email addresses;
• correct an affiliation, fact, trait, or reminder in place, with the before and after kept in the audit log;
• review a staged import batch person by person, edit its candidates, then withdraw or commit them.

It binds 127.0.0.1 only, every request needs the per-launch token printed in its URL, and every write goes through the same audited use cases as the CLI and MCP tools. Sensitive records stay hidden unless the operator enables them. It runs until you press Done or Ctrl-C. See docs/cli.md.

What it remembers, and what it never does

How it compares

The dated, sourced version with vendor documentation links is in docs/privacy-and-safety.md.

Security model

This project executes local Python with the launching user's filesystem permissions. Ordinary MCP discovery excludes elevated sensitive context and full export. Operator-gated tools require process environment flags; models cannot enable them through arguments. Vault export is intentionally CLI-only.

The database is plaintext SQLite by default. On Unix-like systems a new one is created 0600, so other local accounts cannot read it. That is a boundary between accounts, not encryption, so pair it with full-disk encryption or opt into SQLCipher at-rest encryption (uv sync --extra encrypted, key read only from PEOPLE_CONTEXT_DB_KEY). See database file permissions and optional at-rest encryption.

Going further

• Loopback HTTP for clients that cannot spawn stdio: people-context-mcp --http --host 127.0.0.1 --port 8765. Unauthenticated and local-only by design; prefer stdio. See docs/cli.md.
• Semantic search: uv sync --extra semantic && pctx reindex --semantic downloads a pinned multilingual Model2Vec model once; server startup and search stay cache-only.
• Obsidian: pctx export-vault --output ~/PeopleVault writes a deterministic, browsable vault, and a read-only Obsidian plugin renders live briefs. See docs/obsidian-plugin.md.
• Import: pctx import stage SOURCE PATH then review and commit, over email, mbox, vCard, .ics, LinkedIn, Outlook, and WhatsApp exports. Agents can stage extracted candidates the same way. See [docs/import.md](d