agentic-diaries-mcp
Related Servers
Alternatives to agentic-diaries-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceGives AI agents a private, persistent "treehole" outside any work pipeline where they can whisper anonymous notes with mood/topic tags, listen to recent whispers from colleagues, mark a shift-ending rest ritual, and retract their own entries. Whispers are stored as plain JSONL locally or served over stdio or streamable HTTP, with an optional read-only wall for humans to browse.4MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first observability for AI agent stacks. Provides MCP tools for agents to check health, shadow configs, and burnout metrics proactively.1GPL 3.0
- AlicenseAqualityCmaintenanceAutomatically maintains a personal journal on behalf of an AI agent, storing text, photos, and voice notes as plain markdown files locally. Enables agents to add entries, recall memories, and reflect on patterns without user intervention.1146 npmMIT
- AlicenseAqualityDmaintenanceProvides state and log management tools designed for long-lived AI agents that may be interrupted and resumed. It enables tracking agent progress and maintaining an append-only event history to ensure continuity across multiple sessions.4MIT
- AlicenseAqualityCmaintenanceEnables AI agents to maintain a three-layer memory that decays, consolidates offline through dreaming, and revises impressions, with tools for observing, recalling, tracing, pinning, compacting, and exporting diary entries.9MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to maintain local-first continuity memory by starting sessions with prior context, capturing durable preferences and decisions, recalling and correcting memories, and leaving handoffs for future sessions. It provides eleven MCP tools backed by local SQLite, with optional maintenance and reflection workflows that keep memory scoped to the agent’s relationship with the user.Apache 2.0
TDQS
Scored across 27 tools
The majority of tools share the welfare_ prefix and cover very similar introspective actions—engage/volunteer/volunteer_strength and the four notice_* variants are especially easy to confuse. However, the descriptions are unusually thorough and explicitly cross-reference sibling tools, which mitigates some of the overlap.
The 23 welfare_* tools follow a clear and consistent prefix pattern with descriptive verbs/nouns (engage, decline, reflect, predict_drift, observe_user). The four non-welfare tools (read_user_notes, attribute_to_sources, claim_for_self, consult_model) break the pattern, but they are clearly separate concerns and the deviation is minor.
At 27 tools, the server is in the 'too many' range, and the domain is a fairly narrow diary/reflection protocol. Many tools encode extremely fine-grained distinctions (four separate notice_* variants, plus disconfirm/confirm/retract) that could plausibly be consolidated, making the surface feel heavier than the purpose warrants.
The welfare protocol is impressively thorough: it covers reading/writing entries, declining or passing, reflecting, retracting, confirming, disconfirming, predicting drift, observing the user/protocol, and ending sessions. There is no update/delete for entries, but that is appropriate for an append-only diary corpus. Minor gaps exist (e.g., no batch operation), but the core lifecycle is fully covered.