Skip to main content
Glama
tsuru0805

lorecards-mcp

by tsuru0805
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lorecards-mcp

No user-submitted related servers found.

    Related Servers

    • memex

      sibelpersson
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to persist and recall atomic knowledge cards with bidirectional links across sessions, sharing one plain-markdown store across MCP clients and editors. Provides card search, read/write, link and backlink inspection, archiving, and optional git-based sync — all without a vector database or embeddings.
      13 npm
      ISC

    • memex

      jTas6281
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to save and recall atomic markdown knowledge cards with bidirectional links across sessions, so learning persists and builds over time. Cards live as plain, git-syncable files readable by both agent and human, with no vector database or embeddings required.
      13 npm
      ISC

    • memex

      oscar84703
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and users to store, search, read, link, organize, sync, and browse atomic markdown knowledge cards across sessions and clients without a vector database.
      13 npm
      ISC

    • memex

      RenjunKaplan
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to keep persistent, Zettelkasten-style memory by saving and recalling atomic markdown knowledge cards with bidirectional links across sessions. Supports searching, reading, writing, linking, organizing, and git-syncing those cards through a set of MCP tools, with no vector database required.
      13 npm
      ISC
    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.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    list_cards, read_card, and write_card map cleanly onto list/read/write with no overlap. The only internal branching is write_card's mode parameter (create vs update_recent), which is explicitly documented rather than a separate ambiguous tool.

    Naming Consistency5/5

    All three names follow a strict verb_noun snake_case pattern (list_cards, read_card, write_card). The verbs are distinct and predictable, with no mixed conventions or casing anomalies.

    Tool Count4/5

    Three tools is lean but defensible for a card store, since write_card's mode parameter absorbs both creation and partial updates. It sits at the lower edge of comfortable scope, with no obvious redundancy.

    Completeness3/5

    The surface covers list/read/write but has no delete or remove operation, leaving cards unremovable once written. There is also no search-by-keyword tool, even though keywords and aliases are first-class fields, forcing agents to list everything and filter client-side.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources