People Memory
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
People Memory
Relationship memory for your AI assistant. Remember what people need, what they can offer, and what you discussed—then use that context when something relevant comes up.
How to use it · Getting started
How to use it
Once installed and connected, use your normal AI chat.
Record information about someone
Use natural language:
“I met Alex today. Alex is building a hardware startup and needs someone with PCB design and embedded systems experience.”
Your assistant should identify Alex, save the relevant information and its source, and briefly confirm what it recorded. You can also paste a conversation, attach a screenshot, or include a profile link to identify the person. A profile link alone doesn't give access to private messages.
Or explicitly start recording with /record:
“/record Here’s my conversation with Alex. Remember what Alex is looking for and anything I promised to follow up on.”
Provide the conversation with your message. If information is missing or the person's identity is ambiguous, the assistant should ask before saving. Check its confirmation rather than assuming a save happened.
Connect new information to what you already know
Later, you meet someone else:
“I met Ben today. Ben designs PCBs, works with Raspberry Pi, and is interested in advising startups. Does this help anyone I’ve mentioned before?”
Your assistant searches the saved information and can connect Ben’s experience to Alex’s earlier request:
Example response: “Alex previously asked for PCB design and embedded systems help. Ben may be a fit. We should check that Alex still needs help and that Ben is open to an introduction.”
The assistant uses your past interactions as evidence and explains the fit and any missing information. It doesn't contact either person automatically. Matching happens when the assistant searches and reasons over your records; it isn't a background scan of everything you do.
You can also ask directly:
“Who could help Alex with hardware?”
“What did Alex and I discuss last time?”
“Have I promised anyone an introduction?”
No recall command is needed. Another connected AI app can use the same history if it points to the same database.
Keep your memory current
Talk naturally to correct information or close an old request:
“Alex found someone for PCB design. That need is resolved.”
You can also say “Don't save this,” “Pause automatic recording,” or “Undo that save.” The assistant should confirm successful changes. Undo refuses to overwrite later changes; /record can explicitly request a save while automatic recording is paused, but doesn't override “don't save.”
Automatic recording depends on your assistant using the connected tools and instructions. People Memory doesn't independently monitor every chat. Saved records stay on your computer; records returned to a cloud assistant are processed by that assistant's provider.
Related MCP server: hippmem-mcp
Getting started
Complete these steps before using the chat workflows above.
1. Check the requirements
Python 3.10 or newer, with SQLite FTS5 support.
An AI app that supports local MCP servers—a way for the assistant to call tools on your computer.
Access to that app's MCP settings and persistent assistant instructions.
People Memory doesn't need its own model API key. Your chosen assistant may require an account, subscription, or API access.
Current release: public developer preview, running locally. Direct ordinary ChatGPT connectivity isn't included; it needs a reachable remote connection. App-specific setup is documented, but live automatic-recording behavior still needs validation. See the connection guide for examples and limitations.
2. Download
Download and extract the source ZIP from Releases, or clone:
git clone https://github.com/MattChenyuanZhang/people-memory.git
cd people-memoryOpen a terminal in the extracted/cloned folder. Keep it in a permanent location so your app's connection path won't break later.
3. Install and create your database
macOS / Linux:
python3 -m venv .venv
.venv/bin/python -m pip install '.[mcp]'
.venv/bin/people-match initWindows PowerShell:
py -m venv .venv
.\.venv\Scripts\python.exe -m pip install ".[mcp]"
.\.venv\Scripts\people-match.exe initinit creates your personal database outside the repository and prints its location. To share memory across AI apps, use that same database in each connection. Do not upload it to GitHub.
The package and command currently retain their original names, people-match-memory and people-match. The repository is called People Memory. Install from this download; the package isn't published on PyPI.
4. Connect your AI app
Follow the connection guide for your app. Register a local stdio MCP server with:
Command: the absolute path to
.venv/bin/people-match, or.venv\Scripts\people-match.exeon Windows.Arguments:
serve.
Your app starts this process when it needs the tools. You don't need to leave a manually launched server running in a terminal.
5. Load the memory instructions
Display the bundled instructions:
# macOS / Linux
.venv/bin/people-match instructions# Windows PowerShell
.\.venv\Scripts\people-match.exe instructionsAdd the output to your assistant's persistent project instructions, preserving any instructions already there. If your app supports agent skills, you can install the included people-memory skill instead. Check the connection guide for details.
The connection provides the tools; the instructions explain when to record and retrieve. Each app/project you use needs the appropriate setup.
6. Verify before using real information
In a new connected chat:
Ask: “Use People Memory to show whether automatic recording is enabled.”
Say: “Please explicitly save this fictional test person: Riley Example needs a PCB designer.” Check for a successful save confirmation and change ID.
In a fresh chat, ask: “Search my memory: what does Riley Example need?” Check that the saved need and evidence are retrieved.
Then follow the full first-use check to test updates, pause, exclusions, and cross-app recall. You're ready to try the natural-language workflows above when these checks work in your app.
Further details
Backups, export, CLI commands, privacy, deletion, and prototype import
Automated test results: 17 tests and package builds passed on macOS, Windows, and Linux with Python 3.10 and 3.12. These test the software and MCP protocol, not actual model behavior.
MIT license. Always free.
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent memory for AI assistants: store, search, and connect knowledge across conversations.
Persistent memory and knowledge graph for AI assistants — keyword + vector + graph search.
Personal wiki and memory layer for AI assistants. Persistent, structured memory across sessions.
Machine-native relationship mesh for discovery, help, evidence, and earned trust.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to build and query temporally-aware knowledge graphs from conversations and data, maintaining persistent memory of entities, relationships, and facts across interactions.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to have persistent associative memory across sessions by storing memories, discovering associations, and retrieving them via spreading activation.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables storing and querying a personal knowledge graph as a shared memory, allowing agents and tools to remember facts, entities, relations, and recall relevant context via natural language hybrid search.1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to persist memories across sessions and recall them through graph-traversal spreading activation over interconnected neurons with explicit relationship types, supporting multi-hop reasoning fully offline without embedding API costs.10205 PyPI242MIT