Skip to main content
Glama
scarletkc

Perenna

by scarletkc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Perenna

No user-submitted related servers found.

    Related Servers

    • gcc-mcp

      yanhao13
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent, structured memory for AI coding agents via a git-like filesystem with branch/commit/merge tools, enabling agents to maintain context across sessions.
      MIT

    • Hypermnesic

      leonardsellem
      A
      license
      A
      quality
      A
      maintenance
      Git-native long-term memory for AI agents: your markdown files are the source of truth, the search index is a disposable projection rebuilt from git, and every memory the agent writes is a reviewable git commit. Served over one OAuth-secured MCP endpoint with hybrid lexical+semantic recall and a gated, git-first commit_note write tool.
      7
      9
      AGPL 3.0

    • gitmem

      KuraPiee
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI coding agents persistent, branch-aware memory and a dependency-tracked task graph by storing decisions, lessons, and tasks as plain JSON and Markdown committed directly into the repository. Agents can record and fuzzy-search past decisions, dump instant project context, and create, claim, complete, and query tasks whose completion automatically unblocks downstream work.
      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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool handles a distinct lifecycle operation: reading/querying, writing/updating, and deleting memories. There is no overlap between the primary actions, and the sub-modes within memory_read are explicitly separated (list, search, get).

    Naming Consistency5/5

    All tool names follow the same memory_verb pattern using clear, lowercase snake_case verbs. The naming makes the operation type immediately obvious and perfectly consistent across the set.

    Tool Count5/5

    Three tools is a compact but complete surface for a permanent memory store. Each tool earns its place, and no redundant or extraneous operations exist.

    Completeness5/5

    The set covers the full lifecycle: create/modify via memory_write, read via memory_read (including list/search/get), and delete via memory_delete. Revision-handling and Git-history recovery details further round out the functionality, leaving no critical gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources