Skip to main content
Glama
Sign In
second-brain-mcp

second-brain-mcp

by myr0IX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to second-brain-mcp

No user-submitted related servers found.

    Related Servers

    • claude-kb

      tenequm
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching and retrieving Claude Code conversation history via hybrid semantic and keyword search, allowing the agent to access its own past interactions.
      71 PyPI
      5
      MIT

    • obsidiyan

      22wayan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to search a shared, sourced corpus of past Claude Code and Codex sessions and curated notes, retrieve full conversations and timelines, and write or extend memory in either a committed or confidential, git-ignored layer. Confidential material is withheld from results unless explicitly requested.
      MIT

    • ccfolio

      Hippensteel
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching and browsing past Claude Code conversations directly from within an active Claude session, with full-text search and cost tracking.
      MIT

    • project-recall

      mishazim
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to search your local project notes and list indexed projects through hybrid keyword and semantic retrieval, returning relevant snippets with file and line references.
      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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: search_history finds candidate exchanges, and read_exchange expands one specific hit into its surrounding raw conversation. The descriptions explicitly state the dependency ('read the raw conversation around an exchange found by search_history'), leaving no risk of misselection.

    Naming Consistency5/5

    Both names follow the same verb_noun snake_case pattern (search_history, read_exchange), and the nouns describe complementary parts of a single retrieval workflow.

    Tool Count4/5

    Two tools is on the thin side, but for a read-only search-and-retrieve server this is the minimal complete pair rather than an accidental omission. It earns its scope tightly, with no redundant or filler tools.

    Completeness4/5

    The dominant workflow (find an exchange, then read its context) is fully covered across both conversation history and Markdown notes. Minor gaps exist, such as no session listing, date/authority filtering, or pagination for long histories, but agents can work around these with query refinement.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources