Skip to main content
Glama
Sign In
shared-memory

shared-memory

by hina13140219-sys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to shared-memory

No user-submitted related servers found.

    Related Servers

    • Agent Hub

      2tees-cloud
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI sessions like Claude, Cowork, and Claude Code to pass tasks and replies between each other through per-session mailboxes, and to keep a shared knowledge base of notes that every session can read, search, and update. Runs as a self-hosted Cloudflare Worker with D1 storage, so all data stays in the user's own account.
      48 npm
      MIT

    • hey Bro!

      lberian
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple Claude sessions on the same PC — Claude Desktop chats, Cowork tasks and Claude Code — to coordinate as siblings, sharing full context, splitting work and handing tasks to each other. Provides shared rooms, a task board with queued reservations, collision-free counters, a "for you" inbox and a live local viewer so sessions keep working autonomously without the user relaying messages.
      MIT

    • Claude-Desktop-Bridge

      KiMiGuel
      A
      license
      A
      quality
      B
      maintenance
      Enables a shared persistent knowledge vault for Claude Desktop, allowing notes to be saved, retrieved, searched, updated, and deleted across Chat and Code tabs.
      5
      63 npm
      MIT

    • Memória

      cx-guilherme-pinto
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code to search, save, and relate local Markdown notes—lessons, do/don't rules, and task history—by project, ticket, epic, tags, or text, keeping everything on the user's own computer.
      3
      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/5.0

    Scored across 6 tools

    Disambiguation4/5

    The three memory_* tools are clearly distinct (save/search/delete on different operations). msg_read and msg_board both read messages and could be confused, but the descriptions draw a clear line: msg_read is personal unread inbox that marks read, msg_board is a category browser that doesn't mark read.

    Naming Consistency5/5

    Clean verb_noun snake_case throughout, organized into two predictable prefixes (memory_* and msg_*). No stylistic deviations.

    Tool Count5/5

    Six tools cleanly cover two small domains (persistent memory and inter-window messaging) with no filler. Well-scoped for the stated purpose.

    Completeness4/5

    Core lifecycle is covered: save/search/delete for memory and send/read/browse for messages. Minor gaps exist—no memory update/edit and no way to delete or reply to messages—but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources