Skip to main content
Glama
liorsolomon

second-brain-mcp

by liorsolomon

Related Servers

Alternatives to second-brain-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Desktop to Obsidian vaults to enable reading, writing, searching, and intelligent organization of markdown notes. It features pre-configured structures for personal and family data management through natural conversation.
      2
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to create, link, tag, search, explore, and synthesize atomic notes through Claude and other MCP-compatible clients. Notes are stored as readable Markdown files with a SQLite index, supporting semantic link types and graph-based discovery of connected ideas.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to read, write, search, and manage an Obsidian vault with tools for notes, tags, folders, and full-text search.
      17 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to capture structured, schema-validated notes into a personal Obsidian vault's inbox and later recall them through ranked keyword search, recency listing, and single-note reading, with reads confined to the vault and no edit or delete access.
      121 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables bidirectional interaction with Obsidian vaults, allowing reading, writing, and organizing notes through Claude.
      MIT

    TDQS

    B3.2/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (capture/write/patch/read/search/archive for notes, connect/log_interaction/who_knows/upsert_person for people). A few overlap: 'person' (everything about a person), 'people_graph', and 'who_knows' all touch the people graph and could be confused, and 'capture' vs 'write' are close. Descriptions mostly disambiguate these boundaries.

    Naming Consistency4/5

    All names are consistently lowercase snake_case, so there is no casing chaos. However the forms are mixed: some are verbs (archive, search, read, capture, patch, connect), some are nouns (context, health, person, people_graph), and some are verb_noun (upsert_person, log_interaction, follow_ups_due), so the pattern isn't fully predictable.

    Tool Count4/5

    17 tools is on the heavier end but justified by a broad domain spanning note CRUD, a people/relationship CRM, daily logs, and vault maintenance. Each tool maps to a distinct workflow, so few feel redundant, though it sits right at the boundary of 'heavy'.

    Completeness4/5

    Lifecycle coverage is strong: notes have capture/write/read/patch/search/archive/link, people have upsert/person/connect/who_knows/log_interaction/follow_ups_due, plus health and context helpers; delete is intentionally omitted. Minor gaps exist (no rename/move of notes, no unlink or inbox-filing operation), but agents can work around them via patch.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues