Skip to main content
Glama
Sign In
LIPiston

obsidian-rag-mcp

by LIPiston
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to obsidian-rag-mcp

No user-submitted related servers found.

    Related Servers

    • Engram

      engram-app
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to index, search, and retrieve knowledge from an Obsidian vault through MCP, combining semantic and keyword search with real-time sync.
      14
      -

    • Obsidian Index MCP Server

      tcsavage
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides semantic search capability over Obsidian vaults and exposes recent notes as resources to Claude through the MCP protocol.
      9
      -

    • Obsidian MCP Server

      andysama-work
      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

    • mcp-obsidian

      ferronicardoso
      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
    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

    A3.6/5.0

    Scored across 7 tools

    Disambiguation2/5

    obsidian_search and obsidian_rag are heavily overlapping: both take a query/question and top_k to retrieve relevant vault content, with only a subtle framing difference. The other tools are distinct, but these two create real ambiguity for an agent.

    Naming Consistency3/5

    Most tools follow an obsidian_verb pattern (obsidian_search, obsidian_list_notes, obsidian_read_note, obsidian_get_config), but obsidian_rag and obsidian_index_status break the convention with an acronym and a noun phrase. The shared prefix helps, but the pattern is inconsistent.

    Tool Count5/5

    Seven tools is well-scoped for an Obsidian RAG server covering indexing, semantic retrieval, note listing/reading, status, and configuration. Each tool occupies a reasonable place in the workflow without obvious bloat.

    Completeness4/5

    The core RAG lifecycle is covered: build/refresh index, search and retrieve context, list/read notes, check index status, and view config. Minor omissions like an explicit index deletion or note write operations are outside the apparent read-only RAG scope.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources