Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to kObsidian MCP

  • Obsidian

    clavia-labs
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    This is a connector to allow Claude Desktop (or any MCP client) to read and search any directory containing Markdown notes (such as an Obsidian vault).
    797 npm
    1,352
    AGPL 3.0

  • obsidian-mcp

    StevenStavrakis
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI assistants to interact with Obsidian vaults, providing tools for reading, creating, editing and managing notes and tags.
    2,778 npm
    733
    MIT

Related Servers

  • obsidian-mcp

    hanzpo
    A
    license
    Not graded
    quality
    D
    maintenance
    Remote MCP server that gives AI agents read/write access to your Obsidian vaults, supporting both local desktop vaults and headless mode.
    2,778 npm
    MIT

  • obsidian-wiki-mcp

    aud1ence
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server that implements Karpathy's LLM Wiki pattern for Obsidian vaults, enabling persistent knowledge storage and BM25 search across AI sessions.
    9 npm
    1
    MIT

  • vault-master-mcp

    mattbotcode
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that treats Obsidian vaults as knowledge graphs, enabling AI agents to traverse wikilinks, assemble token-budgeted context, and search with backlink awareness.
    3 npm
    1
    MIT

  • mcp-obsidian

    NeveuGregor
    F
    license
    A
    quality
    A
    maintenance
    A filesystem-based MCP server for Obsidian vaults that enables LLMs to browse, search, read, write, and edit Markdown notes directly on disk without requiring Obsidian to be running.
    6
    797 npm
    1
    -
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.1/5.0

Scored across 66 tools

Disambiguation4/5

Tools are namespaced by domain (dataview, tasks, links, wiki, etc.) with clear action suffixes, so most are unambiguous. Minor overlap risk exists between similar utilities like links.hubs/links.connections/links.graph and dataview.query vs its sugar subcommands, but the descriptions clarify when to use each.

Naming Consistency5/5

All tool names follow a strict lowercase domain.action dotted convention (e.g., dataview.index, tasks.toggle, wiki.lint). No mixed casing or inconsistent separators. The one outlier 'kObsidian' in the server name is product branding, not a tool name.

Tool Count3/5

66 tools is a large surface. Many are justified (dataview sugar commands, per-link-type tools), but there's redundancy such as wiki.query/dataview.listByTag vs dataview.query, and links.hubs/links.connections/links.graph which all traverse the graph. Could be consolidated.

Completeness4/5

Covers the Obsidian ecosystem broadly: notes CRUD, tasks, dataview queries, links, blocks, workspace, wiki scaffolding, stats, and graph exploration. Missing a general vault-wide text search tool (a core Obsidian feature) and explicit dataview field update/write utilities; the bundle leans heavily read-only with a few mutations.

Maintenance

ActivityMaintained
ResponsivenessWithin a week

Resources