Skip to main content
Glama
jzhao234

big-brain

by jzhao234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to big-brain

No user-submitted related servers found.

    Related Servers

    • second-brain-mcp

      pthieenlong
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to capture, search, update, and delete notes in a local Markdown vault with automatic categorization and tagging, making knowledge management seamless.
      2 npm
      1
      MIT

    • mcp-vault-reader

      LucasRocha179
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search, read, and traverse Markdown note vaults (Obsidian-compatible) with full-text search, backlinks, knowledge graphs, and a persistent memory system for cross-session context.
      16
      13 npm
      4
      MIT

    • noetrail-mcp

      patsch1
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to capture, search, relate, review, and safely update a local-first Markdown knowledge vault through typed operations such as inventory, retrieve, run_view, update, add_attachment, trash, and restore. Agents get validated access to personal notes and attachments without a generic shell or arbitrary filesystem access.
      28
      60 PyPI
      Apache 2.0

    • Flint Note

      disnet
      A
      license
      B
      quality
      F
      maintenance
      Provides an agent-first note-taking system designed from the ground up for AI collaboration. Organizes your notes as a local vault of ordinary markdown files with semantic note types.
      28
      131 npm
      10
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (notes vs tasks vs projects vs daily notes), and descriptions actively steer between near-neighbors like append_note vs replace_note_body and list_notes vs search_notes. The main soft spot is note_links vs related_notes, both graph/context-exploration tools whose boundaries require reading the descriptions carefully.

    Naming Consistency4/5

    All names use snake_case consistently, which keeps the set readable. However, verb-first (list_notes, create_note, update_task) is mixed with noun-first naming (note_links, related_notes, daily_note, daily_log, brain_overview, vault_health), so the pattern isn't fully predictable.

    Tool Count4/5

    At 23 tools the set is on the heavy side, but the domain is genuinely broad (notes, tasks, projects, daily notes, search, graph, and vault health), and nearly every tool maps to a distinct operation. It is slightly over what one would want but not padded.

    Completeness4/5

    Coverage is strong: notes support create/read/append/replace/frontmatter/archive plus search, links, and related notes; tasks have add/complete/update/list; projects have create/list/status. Minor gaps remain, notably no unarchive/restore to pair with archive_note and no note move/rename operation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources