Skip to main content
Glama
yanglinfeng

Memory Bridge

by yanglinfeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Memory Bridge

No user-submitted related servers found.

    Related Servers

    • mindpalace

      luthfanwakan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to ingest documents and notes, retain facts with their validity periods, and answer questions as of any point in time using bitemporal queries.
      MIT

    • unified-memory-mcp

      sportlotto-ux
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides MCP clients with persistent storage, hybrid search, evidence checking, and automatic context compression, including fact slots, typed links, and lossless archival.
      MIT

    • MCP Shared Memory Hub

      shirisha456
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple MCP-compatible AI clients to share persistent, versioned project knowledge across sessions with conflict-safe updates, provenance, hybrid retrieval, stale-memory handling, and context-budgeted recall.
      MIT

    • Knoverge

      gynsus
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables humans and AI agents to share canonical, versioned knowledge through MCP, with auditable provenance, review workflows, and reconciliation.
      1
      Apache 2.0

    • genpark-agent-hierarchical

      Alpha-Park
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM clients to manage hierarchical working, dialogue, and episodic memories with decay-aware consolidation, hybrid lexical/vector retrieval, knowledge-graph expansion, and semantic caching over MCP.
      7
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools are clearly distinct: memory_remember/forget/update cover the write lifecycle, while answer_calculator/date_diff/date_shift are unambiguous utility functions. The one real overlap is memory_recall vs memory_get_context, which both retrieve relevant long-term memories and differ mainly in output format, so an agent could occasionally pick the wrong one.

    Naming Consistency4/5

    Two clear prefix groups (memory_* for 7 tools, answer_* for 3) give a predictable pattern, and snake_case is used throughout. Minor deviations exist: some names are verb-led (memory_forget, memory_update) while others are noun-led (memory_stats, answer_calculator), and memory_get_context is a longer compound, but all remain readable.

    Tool Count5/5

    Ten tools is well-scoped: seven cover the memory lifecycle and three provide computation helpers that support answering questions from recalled data. Each tool earns its place with no redundant entries.

    Completeness4/5

    The memory surface covers full CRUD plus listing and stats (remember, recall/get_context, update, forget, list, stats), which is a complete lifecycle. Minor gaps exist around namespace/bulk management and export, and the added calculator/date tools are helpful but arguably outside the core memory domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources