Skip to main content
Glama
gavinsomers

obsidian-mcp-context

by gavinsomers

Related Servers

Alternatives to obsidian-mcp-context

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Serves a local Obsidian markdown vault over MCP, enabling agents to search, read, build context, verify, and safely propose or apply guarded changes to the knowledge base.
      12
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients to read, search, and write to a local Obsidian vault over MCP, with full-text search, vault analytics, health scoring, and policy-enforced file operations.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes a typed, provenance-aware knowledge graph over an Obsidian vault to coding agents over MCP, so they can trace what grounds a claim, compute which other notes a change makes wrong, surface contradictions and admitted gaps, and assemble a task-specific token-budgeted subset of the vault. Indexing, retrieval, and impact analysis run with zero third-party runtime dependencies beyond the Python standard library.
      10
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables natural language interaction with a local Obsidian vault, allowing MCP clients to read, search, create, append, and delete markdown notes securely.
      7
      1,052 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes an Obsidian notes vault as MCP services, enabling AI assistants to search, read, create, update, and delete notes and folders.
      10 npm
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a specific aspect of the vault context: get operations for different entity types (entity, note, person, project), list operations for distinct entity attributes (decisions, risks, open loops, tasks, etc.), and search operations. There is no meaningful overlap; every tool has a clearly distinct purpose.

    Naming Consistency5/5

    All tools follow a consistent verb_vault_noun pattern with snake_case (e.g., get_vault_entity_context, list_vault_entities, search_vault_blocks). The use of 'vault' as a prefix is uniform, and the verbs are limited to get, list, and search. Minor singular/plural variations (entity vs. entities) do not disrupt the predictable structure.

    Tool Count4/5

    With 19 tools, the server is slightly above the typical well-scoped range (3-15) but still reasonable given the breadth of entity types and operations. Each tool seems justified for the domain of vault context retrieval, so the count is appropriate.

    Completeness4/5

    The tool set covers a wide range of read operations: getting specific entity contexts, listing various entity attributes and events, and searching. Minor gaps exist, such as the absence of get operations for individual decisions, risks, or tasks (only list is available). However, agents can still retrieve needed information through filtering, so the surface is nearly complete for a read-only context server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues