Skip to main content
Glama
eddyflores100-lang

memex

by eddyflores100-lang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to memex

No user-submitted related servers found.

    Related Servers

    • local-recall-mcp

      Chikoku-NEKO
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides fully local long-term memory for AI agents by enabling semantic search over notes and session logs using Ollama embeddings, with no external APIs or databases.
      MIT

    • Link

      gowtham0992
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.
      186
      MIT

    • SharedBrain

      awictor
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first, multi-user shared memory for AI agents with semantic search, offline support, and team synchronization.
      MIT

    • ContextKeep

      mordang7
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides infinite long-term memory for AI agents with persistent, searchable storage of project details, preferences, and snippets. Reduces token costs by retrieving only relevant memories while keeping all data stored locally.
      157
      MIT

    • ClawMem MCP Server

      BFLabsAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.
      52 npm
      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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: recall searches, store adds, correct supersedes, get fetches by id, recent lists by time, and health checks backend status. There is no overlap, and the descriptions actively redirect misuse to the correct tool.

    Naming Consistency5/5

    All tools share the memex_ prefix followed by a single lowercase word, forming a predictable memex_<operation> pattern. While recent and health are not verbs, the naming is uniform and immediately readable.

    Tool Count5/5

    Six tools is a well-scoped size for a memory system: search, store, correct, retrieve, list, and health cover the core operations without redundancy. Each tool earns its place and the count feels neither thin nor heavy.

    Completeness5/5

    The surface covers the full memory lifecycle: storing, searching, retrieving by id, correcting with supersession, recency listing, and backend health. Deletion is intentionally omitted with supersession used instead, so there are no dead ends in the intended workflow.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources