Skip to main content
Glama
alex106

obsidian-secondbrain-mcp

by alex106
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to obsidian-secondbrain-mcp

No user-submitted related servers found.

    Related Servers

    • Nexus MCP for Obsidian

      ProfSynapse
      A
      license
      Not graded
      quality
      A
      maintenance
      Turns your Obsidian vault into an MCP-enabled workspace with tools for reading/writing notes, managing folders, running semantic searches, and maintaining long-term memory—all while keeping data local to your vault.
      149,900 npm
      153
      MIT

    • vault-search-mcp

      everton-dgn
      A
      license
      B
      quality
      A
      maintenance
      Enables local hybrid search over Obsidian and Markdown vaults via MCP, combining vector retrieval, full-text search, reranking, graph navigation, and safe CRUD while keeping data local.
      43
      MIT

    • okc-mcp

      dolgogae
      A
      license
      Not graded
      quality
      C
      maintenance
      A local Obsidian Vault authoring MCP for building high-quality knowledge inputs for OKC, enabling note creation, search, and audit without the Obsidian app.
      MIT

    • Vault MCP

      Aidan-Kay
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables hybrid search, reading, writing, and managing a local Obsidian vault through MCP tools and a REST API, including section patching, appending, moving notes with link rewriting, and frontmatter updates.
      AGPL 3.0

    • brain-mcp

      irahulstomar
      A
      license
      Not graded
      quality
      D
      maintenance
      A private, local AI second brain for Markdown notes, providing hybrid search and read/write tools for MCP-compatible AI clients like Claude and Cursor.
      6
      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

    B3.4/5.0

    Scored across 27 tools

    Disambiguation5/5

    Every tool targets a distinct operation: listing paths vs. searching by name/content/tag/frontmatter, editing via distinct primitives (create/append/patch/frontmatter), and graph-specific tools (related, backlinks, stale, recent). The search tools are clearly separated by what they search (name vs. content vs. tag vs. frontmatter), minimizing confusion. Even the distillation workflow tools (capture_session, log_entry, distill_queue, mark_distilled) each have non-overlapping responsibilities.

    Naming Consistency4/5

    Most tools follow verb_noun snake_case (create_note, move_note, search_notes, build_map). A few are noun-first (vault_info, vault_health, backlinks) and one adjective_noun (distill_queue). The convention is predominantly consistent, and any deviations are clear from context. The minor inconsistency keeps it from a perfect score.

    Tool Count4/5

    At 27 tools, this exceeds the typical 15-tool threshold, but the server manages a full Personal Knowledge Management system: CRUD, multiple search modes, graph analytics, session capture, distillation workflow, health checks, and map building. Each tool addresses a distinct need, so the count feels justified rather than bloated. It is on the heavy side but appropriate for the scope.

    Completeness5/5

    The tool surface is remarkably complete for a second-brain vault: full note lifecycle (create, read, append, patch, move, archive without deletion), comprehensive search (name, content, tag, frontmatter), graph operations (backlinks, related, stale, recent), a distillation pipeline (capture, log, distill, mark_distilled), and maintenance utilities (health, map, resurface). The only missing operation is permanent deletion, which is a deliberate design choice. This is a fully realized workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources