Skip to main content
Glama
RasAlGhul96

Obsidian MCP Server

by RasAlGhul96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Obsidian MCP Server

No user-submitted related servers found.

    Related Servers

    • obsidian-mcp

      martinblq
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects Claude to a local Obsidian vault, enabling listing, reading, searching, and optionally editing notes via natural language, with all operations running locally.
      2,509 npm
      MIT

    • obsidian-mcp

      jason-c-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading, writing, searching, and managing an Obsidian vault through Claude, operating directly on markdown files via Node.js fs without requiring the Obsidian app.
      5,145 npm
      MIT

    • obsidian-mcp-server

      FAL1989
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to interact with an Obsidian vault through the Local REST API, allowing file listing, reading, searching, creating, and updating markdown notes.
      5,145 npm
      Apache 2.0

    • vault-ask

      burakozg
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Code and Claude Desktop retrieve and explore an Obsidian vault through tools for semantic search, reading notes, following graph neighbors, and listing topics.
      MIT

    • obsidian-mcp

      bbdaniels
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code read/write access to an Obsidian vault, including creating, editing, searching, and browsing notes.
      8
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: reading a single note, listing notes recursively, and searching for content across notes. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: read_note, list_notes, search_vault. The naming convention is uniform and predictable.

    Tool Count5/5

    Three tools is well-scoped for a read-only Obsidian vault server. Each tool earns its place and covers the essential read/query operations without redundancy.

    Completeness5/5

    For a read-only server, the surface is complete: you can read, list, and search notes. There are no obvious gaps for the stated purpose of accessing and searching vault content.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources