People Context

Name: People Context
Author: JinyangWang27

by JinyangWang27version 1.5.0i★ –iRuns on your computer

Registry nameio.github.JinyangWang27/people-context

Install

Overview

Description from the maker (original English)

Local-first MCP server giving AI agents contextual knowledge about the people in your life

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: Search & AI memory

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).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx 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": {
    "people-context": {
      "command": "uvx",
      "args": [
        "people-context"
      ]
    }
  }
}

Run this in your terminal

claude mcp add people-context -- uvx people-context

Open in Cursor

Or copy the settings yourself

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

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

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": {
    "people-context": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "people-context"
      ]
    }
  }
}

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.

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 JinyangWang27, 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 Search & AI memoryi

More stars than 0% of the other 5655 servers in this category
Published to the registry more recently than 96% of the other 5655 servers in this category
Basic checks equal to or better than 100% of the other 5655 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 People Context 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 (1.5.0) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago

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.

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

It remembers	It never does
Names, nicknames, aliases, and handles	Upload anything, anywhere
Relationships with a canonical, extensible vocabulary	Store raw imported emails, chats, or files
Organisations, roles, and time-bounded affiliations	Let a model enable sensitive disclosure or full export
Durable facts, observations, and traits with evidence	Commit imported or agent-extracted data without your review
Concise interaction summaries and a per-person timeline	Log private values or keep a soft-deleted copy after `forget`
Reminders, follow-ups, and your communication philosophy	Make a network request outside `pctx reindex --semantic`

How it compares

	`people-context`	Assistant memory (ChatGPT, Claude)	Memory platforms (Mem0 and similar)
Where data lives	One SQLite file you own	Vendor account	Vendor platform or your own deployment
Works offline	Yes	No	Self-hosted only
Knows people as first-class records	Identity, relationships, roles, graph, guidance	Free-text notes	Free-text or vector memories
Explains a match	Ranked candidates with a reason; ambiguity is surfaced	No	Similarity score
Import review gate	Stage, review, commit	n/a	Automatic extraction
Deletion	Hard delete plus audit redaction in one transaction	Request to vendor	API delete
Backup and move	`pctx sync push` / `pull` bundle	n/a	Deployment-specific

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

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

People Context

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

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 Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

people-context

Why

Demo

Quick start

Review and edit in your browser

What it remembers, and what it never does

How it compares

Security model

Going further