Skip to main content
Glama
akaiserg

MCP Memory Tracker

by akaiserg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to MCP Memory Tracker

No user-submitted related servers found.

    Related Servers

    • Mem0 MCP Server

      ryaker
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that integrates AI assistants with Mem0.ai's persistent memory system, allowing models to store, retrieve, search, and manage different types of memories.
      16
      MIT

    • STRATA

      ssundxr
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides AI assistants persistent context memory across sessions, using Supabase PostgreSQL and pgvector to save, search, list, and delete memories via natural language.
      623 npm
      -

    • mem0-agent-memory

      arunkumars-mf
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides persistent memory capabilities for AI agents using Mem0, enabling storage, search, and management of contextual information across conversations with support for multiple backends and LLM providers.
      18
      24 PyPI
      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/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one saves memories and the other searches memories. There is no overlap or ambiguity between these operations, making it easy for an agent to select the correct tool based on the intended action.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (save_memory, search_memories) with clear, descriptive verbs. The naming is uniform and predictable, adhering to snake_case throughout without any deviations.

    Tool Count2/5

    With only two tools, the server feels thin for a memory tracker domain. While save and search are core operations, typical memory systems might also include update, delete, list, or clear functions. The count is too low for comprehensive coverage, limiting agent capabilities.

    Completeness2/5

    The tool surface is significantly incomplete for a memory tracker. It lacks essential operations like updating or deleting memories, listing all memories, or managing memory categories. This creates dead ends for agents trying to perform full lifecycle management of memories.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources