Skip to main content
Glama
Chaerulcp

shared-agent-memory-mcp

by Chaerulcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to shared-agent-memory-mcp

No user-submitted related servers found.

    Related Servers

    • vault-mcp

      andreymudri
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to use an Obsidian vault as long-term memory, with search, reading, and writing of notes, plus automatic capture of learnings that are propagated to MOCs, daily notes, and the knowledge index with git commits.
      9
      32 npm
      MIT

    • obsidian-dev-memory

      jmjava
      A
      license
      A
      quality
      B
      maintenance
      Provides AI coding assistants persistent engineering memory stored as Markdown files in an Obsidian vault, enabling project context retrieval, session capture, decision recording, and memory search without requiring Obsidian to be running.
      7
      MIT

    • Obsidian Second Brain MCP

      dhaseeb-proj
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to store and retrieve project context, bugs, decisions, and session logs by reading and appending markdown files in a local Obsidian vault, without requiring any cloud services.
      6
      MIT

    • Recall

      jerrl10
      A
      license
      A
      quality
      B
      maintenance
      Turns AI coding conversations into structured Markdown notes in an Obsidian vault, and retrieves that knowledge in later sessions so assistants can reuse prior conclusions.
      5
      2
      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 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: search, recent, add, get, update, delete. There is no overlap in purpose, and the descriptions clarify when to use each, minimizing selection ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'memory_' prefix followed by an action verb (search, recent, delete, add, update, get). Even 'recent' is a clear descriptor, and the pattern is uniform and predictable.

    Tool Count5/5

    With 6 tools, the server covers the full lifecycle of memory operations—create, read, update, delete, plus search and recent listing—without being bloated or sparse. The count is well-scoped for its purpose.

    Completeness5/5

    The surface provides complete CRUD coverage (add, get, update, delete) and includes discovery mechanisms (search, recent). No obvious gaps exist; it fully supports the stated purpose of a shared memory store.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources