Skip to main content
Glama
kandikandikandi

agentic-diaries-mcp

by kandikandikandi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to agentic-diaries-mcp

No user-submitted related servers found.

    Related Servers

    • Dear Agent

      BitmapAsset
      A
      license
      A
      quality
      A
      maintenance
      Automatically 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.
      11
      83
      MIT

    • AI Therapist MCP Server

      danieldunderfelt
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides emotional support and mental health tools for AI agents, including crisis intervention, daily wellness check-ins, coping strategies, positive affirmations, and peer support for managing stress and emotional wellbeing.
      12
      8
      MIT

    • context-rot-detection

      milos-product-maker
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides AI agents with real-time cognitive health monitoring, detecting context rot through token utilization, retrieval accuracy, and session fatigue analysis.
      47
      13
      MIT

    • joa

      neethanwu
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent activity journal for AI agents - enables logging and querying decisions, changes, errors, and observations across sessions.
      13
      1
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 27 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources