Skip to main content
Glama

Related Servers

Alternatives to lorecards-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides long-lived, cross-project technical memory for AI agents via markdown cards stored in git and indexed by SQLite, enabling search, retrieval, and human-reviewed knowledge management.
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      Exposes tools that let an agent search a local Markdown-based memory store, fetch full cards by id, write new knowledge cards that are indexed immediately, and inspect or rebuild the SQLite index. All retrieval runs locally over Chinese-friendly full-text search with graded exact/prefix matching, so agents without a memory system can recall prior notes while existing Markdown files stay read-only.
      5
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage a personal markdown-based knowledge base with natural language interactions. Supports creating, searching, updating, and organizing notes across categories like people, recipes, meetings, and procedures.
      11
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search, read, create, update, and remove personal markdown notes stored locally, providing persistent memory across sessions.
      60 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to maintain a persistent, queryable memory stored as user-owned Markdown files, with dual-channel retrieval (FTS5 and optional semantic search) and an audited write pipeline.
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to save, search, and manage markdown-based research articles through a complete CRUD interface. Supports creating, reading, updating, and deleting articles with frontmatter metadata in a self-hosted file-based system.
      2
      MIT

    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

    ActivityMaintained
    ResponsivenessNo issues