people-context
Related Servers
Alternatives to people-context
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceAn MCP server that gives AI agents a private, durable memory of people, providing a personal people graph in PostgreSQL with tools to search, remember, and connect people, plus imports from LinkedIn, Google Contacts, and WhatsApp, and a browser UI.111MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP memory server providing persistent, searchable memory for AI agents, powered by SQLite.1 npm1Apache 2.0
- AlicenseAqualityFmaintenanceLocal-first MCP memory server that gives AI coding agents long-term memory via SQLite and sqlite-vec, with optional LLM-powered layering. No gateway or API key required.7102 npm4MIT
- AlicenseNot gradedqualityFmaintenanceLocal-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.2Apache 2.0
- AlicenseCqualityAmaintenanceLocal-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.4031 PyPI1MIT
- FlicenseNot gradedqualityCmaintenanceLocal-first cross-agent memory for AI coding agents. Persistent, shared memory over MCP — what you tell one agent can be recalled by another — with all data stored in a single local SQLite file, no cloud and no API keys.-
TDQS
Scored across 41 tools
Most tools target a distinct resource and action, and detailed descriptions separate similar readers like get_person_context, get_consolidation_context, and get_person_timeline. Some overlap remains between the broad remember convenience tool and the specialized record_*/set_* writers, but the descriptions give clear usage guidance.
The naming is predominantly snake_case verb_noun and generally predictable (get_*, record_*, set_*, find_*, list_*). Minor deviations like semantic_search, upcoming_dates, and forget, plus mixed verb choices across create/set/add/record, keep it from being fully consistent.
41 tools is well beyond the typical well-scoped range and exceeds the 25+ threshold for a heavy surface. While the domain is broad, several tools overlap in purpose and could be consolidated, such as remember versus the record_* family and the multiple get_* context variants.
The tool surface covers the main lifecycle well: identity, facts, traits, interactions, relationships, affiliations, groups, reminders, imports, corrections, merges, and deletion. Minor gaps exist, such as no dedicated end/remove operation for affiliations or relationships and no batch listing for staged imports, but these are workable.