Skip to main content
Glama
codeafix

obsidian-mcp-guard

by codeafix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to obsidian-mcp-guard

No user-submitted related servers found.

    Related Servers

    • Cursidian

      CoolJohn-lab
      A
      license
      A
      quality
      B
      maintenance
      Enables Cursor agents to read, write, search, and manage local Obsidian vaults via 13 tools with safe writes and direct filesystem access.
      4
      MIT

    • gosidian

      daniele-chiappa
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with typed tools to bootstrap sessions, ingest files, search, read, write, link, handoff, self-check, and audit markdown notes in a self-hosted Obsidian-compatible vault.
      1
      MIT

    • obsidian-mcp

      ubahmapk
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients to read, create, edit, delete, move, and search notes in local Obsidian vaults via direct filesystem access, including tag management and support for multiple vaults.
      MIT

    • obsidian-vault-mcp

      RyanMelena
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to search, read, and write notes in an Obsidian vault, including creating and updating notes in an inbox and syncing changes with Gitea/GitHub.
      MIT

    • mcp-obsidian-vault

      t-rhex
      A
      license
      A
      quality
      C
      maintenance
      Provides AI agents with direct filesystem access to an Obsidian vault for note management, task orchestration, context persistence, and git synchronization.
      27
      50 npm
      2
      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 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: create, read, update, delete, move, list, and lint. No two tools overlap in purpose, so an agent can clearly differentiate them.

    Naming Consistency5/5

    All tool names follow the verb_note/verb_notes pattern (delete_note, move_note, lint_note, read_note, list_notes, create_note, update_note), demonstrating a highly consistent naming convention.

    Tool Count5/5

    Seven tools is a well-scoped set for a note management server, covering the essential operations without unnecessary bloat or sparse coverage.

    Completeness4/5

    The set covers the full CRUD lifecycle plus move, list, and lint, but the descriptions reference a search_notes tool that is not exposed. This creates a potential dead end for agents that rely on that referenced capability.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources