lifedb-mcp
Related Servers
Alternatives to lifedb-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceA native macOS app with a read-only stdio MCP server for searching a local work timeline by app, document, optional Chrome page context and time. Requires Apple silicon and macOS 15+; it runs on the user’s Mac, rather than in Docker or as a hosted endpoint.8MIT- AlicenseNot gradedqualityCmaintenanceEnables any MCP client (zcode, Claude Code, Cursor) to give its model bi-temporal long-term memory, auditable evidence-cited retrieval, LLM-assisted document extraction, and deterministic A* skill planning with precondition/effect verification. All four capabilities share one portable SQLite store and can be mounted independently on demand.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.392 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools to read and update a local-first personal OS for goals, tasks, habits, food, workouts, and check-ins. Enables assistants to manage daily life data and interact with an evidence-grounded AI coach.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store, query, and trace a time-aware memory graph of nodes and edges in a single SQLite file, supporting weighted recall, temporal queries, and provenance-aware writes over MCP.4 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables any MCP-capable AI app to read and write a single, locally stored, user-owned journal file, so memory persists across different assistants without a cloud account. Entries are append-only and cryptographically chained, with tools for waking briefings, writing notes, searching, pinning, verifying integrity, and exporting backups.AGPL 3.0
TDQS
Scored across 7 tools
Most tools have a clear distinct intent: stats (metadata self-check), query_month (monthly timeline), around (ts-window union), geo_track (GPS-only points), export_atlas (bundled atlas for an app), ingest_jsonl (write), adapters (plugin listing). There is mild overlap between around, geo_track, and export_atlas since all read time-windowed event/GPS data, but the granularity (point vs month vs track vs bundle) keeps them separable.
All names share the lifedb_ prefix, giving a strong consistent identity. However the verb_noun pattern is not uniform: query_month, geo_track, export_atlas, ingest_jsonl follow it, while stats, around, and adapters are bare noun/adverb forms.
Seven tools is well-scoped for a personal life-database server: four read/query tools, one export, one ingest, and one metadata/introspection tool. Each tool appears to earn its place without redundancy.
The read surface covers timelines, point windows, GPS tracks, and atlas bundles, and ingest is idempotent, but there is no update/delete or prune operation for events, no fetch-by-id, and no free-form range or modality/text search beyond month windows and the atlas export. These gaps force workarounds for correction and targeted retrieval.