Skip to main content
Glama
YuNaga224

Obsidian Memory MCP

by YuNaga224

Related Servers

Alternatives to Obsidian Memory MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to have persistent memory by storing facts and transcripts as markdown files in an Obsidian vault, allowing manual editing and immediate effect without sync.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent long-term memory for AI assistants with tag-based retrieval, wiki-style linking, and source references, storing memories as markdown files with SQLite index.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to preserve and share knowledge as plain Markdown files in a local folder the user owns, with tools to remember, recall, get, update, forget, and list scopes. Memories are stored by scope, versioned rather than overwritten, and readable or editable in Obsidian or any text editor.
      2
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Basic Memory is a knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md
      17
      7,603 PyPI
      4,114
      AGPL 3.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory for AI agents enabling saving, searching, and managing knowledge across sessions with local markdown files.
      -

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific operations on the knowledge graph: adding/deleting observations, creating/deleting entities/relations, opening/reading/searching nodes. No overlap exists; for example, 'create_entities' and 'create_relations' are distinct, and 'open_nodes' and 'search_nodes' serve different access functions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout: 'add_observations', 'create_entities', 'delete_relations', etc. The naming is predictable and readable, with verbs like 'add', 'create', 'delete', 'open', 'read', and 'search' applied consistently to their respective nouns.

    Tool Count5/5

    With 9 tools, the count is well-scoped for managing a knowledge graph, covering core operations like CRUD for entities, relations, and observations, plus graph access. Each tool earns its place without bloat, fitting a typical range of 3-15 tools for this domain.

    Completeness4/5

    The tool set provides strong coverage for knowledge graph management, including create, read, delete, and search operations. A minor gap exists in update capabilities (e.g., no 'update_entities' or 'update_relations'), but agents can work around this by deleting and recreating, and core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues