Skip to main content
Glama
LIPiston

obsidian-rag-mcp

by LIPiston
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to obsidian-rag-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      13 npm
      1
      MIT

    • Semantic Notes Vault MCP

      aaronsb
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI assistants to an Obsidian vault as a semantic knowledge graph, enabling graph navigation, semantic search, and content operations through MCP.
      2 npm
      465
      MIT

    • vault-vector

      All-zen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables semantic and full-text search over markdown notes, with tools to create, edit, move, and delete notes, all through MCP. Runs entirely locally using Ollama for embeddings and SQLite for storage, working with Obsidian or standalone.
      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

    ActivitySlowing
    ResponsivenessNo issues

    Resources