Skip to main content
Glama
alfianyusufabdullah

jalipata-mcp-memory

by alfianyusufabdullah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to jalipata-mcp-memory

No user-submitted related servers found.

    Related Servers

    • Mnemosyne

      M4F-S
      A
      license
      A
      quality
      A
      maintenance
      Provides persistent, graph-based memory for AI agents via MCP, enabling semantic search, wikilink traversal, reminders, and injection protection.
      9
      30
      Apache 2.0

    • Librarian

      arcadeai-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with persistent knowledge storage, enabling them to store, search, and retrieve text, documents, and files using semantic and keyword search via MCP tools.
      32
      Apache 2.0

    • Agent Memory

      Masikomoore
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.
      3
      -

    • ContextForge

      vikas-1rai
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents and IDEs to capture conversations, extract structured knowledge into a queryable graph database, and recall past decisions, patterns, files, and errors across all projects and workspaces. Provides persistent memory tools for saving, searching, and cleaning up knowledge via MCP.
      2
      -
    • HAM by MonumentalSystems

      HAMofficial

      MonumentalSystems
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent, scoped shared memory for collaborating AI agents, with tools for storing observations, semantic recall, and handoff workflows. Backed by PostgreSQL and exposed through MCP.
      1
      Apache 2.0
    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

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct operation: creating entities, creating relations, adding observations, and deleting each of those, plus distinct retrieval methods (read graph, search, open by name) and namespace listing. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (create_entities, delete_relations, open_nodes, etc.). The only slight variation is 'add_observations' versus 'create_*', but 'add' is still a clear active verb in the same style.

    Tool Count5/5

    With 10 tools, the server is well-scoped for a knowledge graph memory system. Each tool covers a essential operation without redundancy, and the count is within the ideal range for a focused server.

    Completeness4/5

    The surface covers the full CRUD lifecycle for entities, relations, and observations, plus retrieval and namespace listing. Minor gaps exist such as no update/rename operation for entities or relations, but these are not critical for typical memory graph workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources