Skip to main content
Glama
diegorv

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Another bloated Obsidian MCP Server

No user-submitted related servers found.

    Related Servers

    • Obsidian MCP

      takuya0206
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to read, write, and manipulate notes in your Obsidian vault through a standardized interface.
      5
      2,778 npm
      4
      ISC

    • Obsidian MCP Server

      CtrlAltAdapt
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides AI assistants with access to your Obsidian vault through the Obsidian Local REST API plugin.
      6,222 npm
      Apache 2.0

    • obsidian-headless-mcp

      seb7152
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides tools and resources for AI models to interact with an Obsidian vault, enabling file operations, search, and management via the Model Context Protocol.
      2
      -

    • Obsidian MCP

      newtype-01
      A
      license
      A
      quality
      F
      maintenance
      This project implements a Model Context Protocol (MCP) server for connecting AI models with Obsidian knowledge bases. Through this server, AI models can directly access and manipulate Obsidian notes, including reading, creating, updating, and deleting notes, as well as managing folder structures.
      11
      56 npm
      311
      MIT

    • obsidian-local-mcp

      MatthewSuazo
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that wraps the Obsidian CLI to give AI assistants direct access to read, edit, and manage notes within an Obsidian vault. It enables advanced operations such as frontmatter property management, context-aware searching, and the execution of internal Obsidian commands.
      2
      -
    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 50 tools

    Disambiguation3/5

    Most tools have clear, distinct purposes, but there are overlapping pairs such as get_daily_note and create_daily_note (both create if missing), and add_tag vs add_to_array_field for managing tag arrays. The descriptions help, but with 50 tools, some ambiguity remains.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., list_vaults, read_note, batch_move). Prefixed batch operations and specific verbs like get/list/find/query are used predictably, making the naming highly uniform.

    Tool Count2/5

    With 50 tools, the server is excessively large for most use cases. The name itself suggests bloat, and while the domain is broad, many tools are redundant or could be combined (e.g., batch operations, frontmatter fields). This crosses the 25+ threshold for 'too many'.

    Completeness4/5

    The toolset covers a comprehensive range of Obsidian vault operations: note CRUD, frontmatter, tags, links, daily notes, templates, bases, attachments, and backups. Minor gaps exist (e.g., no explicit folder listing, but folders are implicit in paths), and some redundancies, but no critical dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources