Skip to main content
Glama
marwansaab

obsidian-modified-mcp-server

by marwansaab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to obsidian-modified-mcp-server

No user-submitted related servers found.

    Related Servers

    • Optimike Obsidian MCP

      optimikelabs
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Obsidian that exposes tools for reading/writing notes, managing frontmatter and tags, querying Tasks, semantic search, and interacting with Obsidian Bases, with shared local caching and support for various runtime modes.
      39
      Apache 2.0

    • obsidian-brain

      sweir1
      A
      license
      A
      quality
      D
      maintenance
      A standalone Node MCP server that provides semantic search, knowledge graph, and vault editing over an Obsidian vault. It runs locally as a single stdio process without requiring an Obsidian plugin for core functionality.
      18
      80 npm
      10
      Apache 2.0

    • mcp-markdown-vault

      wirux
      A
      license
      B
      quality
      C
      maintenance
      Headless semantic MCP server for Obsidian, Logseq, Dendron, Foam, and any markdown folder. Features built-in hybrid semantic search, surgical AST editing, template scaffolding, zero-config local embeddings, and workflow tracking.
      5
      56 npm
      11
      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

    A3.6/5.0

    Scored across 32 tools

    Disambiguation5/5

    Each tool targets a distinct resource and operation: file reading/writing, search with different query types, vault graph analysis, commands, and periodic notes. The descriptions clearly differentiate similar-looking tools like search, complex_search, pattern_search, and semantic_search.

    Naming Consistency5/5

    Tool names follow a consistent lowercase snake_case convention with a verb-noun structure (put_content, get_file_contents, delete_file, list_tags). Even compound names like batch_get_file_contents and find_and_replace fit the pattern, and search variants share a common suffix.

    Tool Count2/5

    With 32 tools, the server exceeds the typical well-scoped range (3-15) and enters the 'too many' category (25+). While each tool is distinct, the sheer number could overwhelm agents, and some tools could be parameterized to reduce count.

    Completeness4/5

    The surface covers CRUD, search (keyword, regex, semantic, JsonLogic), graph analysis, periodic notes, tags, and command execution. Minor gaps include rename/move operations and explicit folder creation, but the core workflows are well covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources