Skip to main content
Glama
aaronsb

Obsidian Semantic MCP Server

by aaronsb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Obsidian Semantic MCP Server

No user-submitted related servers found.

    Related Servers

    • Obsidian MCP Server

      marcelmarais
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight server that enables AI assistants like Cursor & Claude to read from and write to Obsidian vaults, allowing actions like creating notes, checking existing content, and managing todos through natural language.
      6,347 npm
      32
      Apache 2.0

    • Obsidian MCP Server

      pmmvr
      A
      license
      A
      quality
      D
      maintenance
      A server that enables AI agents to perform sophisticated knowledge discovery and analysis across Obsidian vaults through the Local REST API plugin, supporting complex multi-step workflows with advanced filtering and full content retrieval.
      3
      21
      MIT

    • Obsidi MCP

      cameronsjo
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Obsidian vault tools via Model Context Protocol (MCP) server over stdio, HTTP, or SSE transports, enabling AI assistants to read, write, search, and manage vault notes with 28+ built-in tools and CLI bridge integration.
      1
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: edit handles content modifications, system manages system-level operations, vault deals with file management, view focuses on content display and navigation, and workflow provides contextual suggestions. There is no overlap in functionality that would cause confusion for an agent.

    Naming Consistency5/5

    All tool names follow a consistent, simple noun-based pattern (edit, system, vault, view, workflow) without mixing conventions like camelCase or snake_case. This predictability makes it easy for an agent to understand and select tools.

    Tool Count5/5

    With 5 tools, the server is well-scoped for an Obsidian integration, covering key areas like file operations, content editing, system interactions, viewing, and workflow assistance. Each tool earns its place without feeling excessive or insufficient.

    Completeness4/5

    The tool set provides comprehensive coverage for core Obsidian workflows, including CRUD operations via vault, editing capabilities, and navigation. A minor gap might be the lack of explicit tools for plugin management or advanced search, but agents can likely work around this with existing tools like system and vault.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources