Skip to main content
Glama
Sign In
prospective-memory

prospective-memory

by Daemon-Killer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to prospective-memory

No user-submitted related servers found.

    Related Servers

    • open-brain-mcp

      uwek
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for storing and retrieving thoughts, notes, and ideas with semantic vector search, enabling integration with Claude Desktop and other MCP clients.
      MIT

    • nudge

      davesleal
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that connects AI assistants like Claude to your todo app, enabling natural, friendly reminders and task management without a server to run.
      8
      3 npm
      MIT

    • stafett

      lineaalba2
      F
      license
      Not graded
      quality
      C
      maintenance
      A remote MCP server that gives AI assistants a shared memory, enabling structured handoffs, journaling, and notes for seamless continuation across sessions.
      -

    • cortex

      moguls753
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted personal memory assistant that captures and retrieves thoughts via voice or text, with MCP tools for querying and managing entries.
      67 npm
      AGPL 3.0

    • genmem

      helloSobuj
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that gives AI assistants long-term memory by storing, searching, and recalling notes as Markdown files on your machine.
      14 npm
      MIT

    • memhub

      gaw008
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted remote MCP server that gives multiple AI assistants one shared, plain-Markdown memory of the user's long-lived facts, so context carries across Claude, ChatGPT, Gemini and Grok instead of being repeated. It exposes a small tool set for retrieving context, searching, reading, adding, updating and deleting facts, plus an append-only daily conversation journal, with server-enforced duplicate, sensitive-data and per-identity permission rules.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 17 tools

    Disambiguation4/5

    Tools are mostly cleanly separated by domain: reminders, tasks, phone notifications, cultural items, and music. There is some conceptual overlap between reminders and tasks, and between resolve_music_query and play_music, but descriptions make the intended boundaries workable.

    Naming Consistency4/5

    Most action tools follow a snake_case verb_noun pattern (create_reminder, list_open_tasks, complete_task, play_music). A few read tools use noun-first labels such as task_stats, latest_otp, last_whatsapp, and missed_summary, and create/capture are used inconsistently for similar creation actions, but naming remains readable.

    Tool Count4/5

    At 17 tools the surface is slightly above the ideal 3-15 range, but it covers five distinct subdomains: tasks, reminders, notifications, cultural items, and music. Each tool appears to earn its place rather than being redundant bulk.

    Completeness3/5

    Core flows for tasks and reminders are present: create, list, complete, and for tasks also search/drop/stats. However, there are notable lifecycle gaps: reminders and tasks lack explicit update/edit and delete operations, cultural items can be captured/listed but not marked consumed, and music playback has no stop/control counterpart.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources