Skip to main content
Glama
yBookoff

thebrain-mcp

by yBookoff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to thebrain-mcp

No user-submitted related servers found.

    Related Servers

    • moss-brain

      Naut1cal5
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides semantic memory with search, related-content traversal, and write-back capabilities, all powered by local embeddings of your notes, documents, and chat histories.
      3
      MIT

    • mybrain

      robertsfeir
      A
      license
      Not graded
      quality
      C
      maintenance
      A personal knowledge base MCP server with semantic search, storing thoughts in PostgreSQL with pgvector embeddings and providing 8 tools for capture, search, browse, stats, relations, traces, and hydration.
      1
      Apache 2.0

    • brain-mcp

      victorsabino
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server exposing personal knowledge base tools, including save, search, get, context, link, and feedback, backed by brain-cli's SQLite database.
      MIT

    • Graph-Mem MCP

      Sathvik-1007
      A
      license
      Not graded
      quality
      A
      maintenance
      A universal MCP server providing persistent, structured memory through a knowledge graph with graph storage, semantic vector search, and multi-hop traversal for AI agents and IDEs.
      1
      MIT

    • hybrid-recall

      cutlerbenjamin1-cmd
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server enabling hybrid search over documents, memory, and knowledge graphs for retrieval-augmented generation, with tools for SQLite, semantic memory, and entity-relationship queries.
      4
      1
      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/5.0

    Scored across 17 tools

    Disambiguation5/5

    Every tool targets a distinct operation: search vs traverse vs get are clearly different (semantic lookup, graph walk, single-thought detail), and create_thought vs ingest are separated by single vs batch. Even similar tools like set_note and append_note are explicitly differentiated by replace vs append semantics.

    Naming Consistency4/5

    All tools use the brain_ prefix with snake_case and descriptive verbs, but a few (brain_activate, brain_list, brain_index) omit an object while the majority follow verb_noun. This is a minor deviation, not a chaotic mix.

    Tool Count4/5

    17 tools is slightly above the usual sweet spot but each one addresses a meaningful capability of the graph system (thoughts, notes, links, tags, index, batch ingest). No tool feels redundant; the count is justified by the domain's scope.

    Completeness4/5

    The surface covers the core lifecycle: list brains, search/get/traverse, create/update/delete thoughts, edit notes, link, tag, attach URLs, and manage the index. Obvious gaps include no explicit unlink or reparent operation, but these can be worked around via update_thought and the graph structure.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources