Skip to main content
Glama
no-carve-only-pizza

SecondBrain

by no-carve-only-pizza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SecondBrain

No user-submitted related servers found.

    Related Servers

    • memory-ai-local

      Hsoley1
      F
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that manages developer memory for coding agents, enabling shared project context, permissions, and audit trails across different agents.
      1
      -

    • mnemo

      JoaquimLegal
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing persistent, local-first memory for AI agents via Markdown files in a git repo, with search, branching, and auditability.
      9 npm
      2
      MIT

    • cookbook-brain

      dpro10
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents persistent, file-based memory stored as plain markdown files in a local git repository, enabling agents to remember, recall, and build on information across sessions.
      6 npm
      1
      MIT

    • Agentic Memory

      ArkaAiAdmin
      A
      license
      A
      quality
      B
      maintenance
      MCP server for persistent, cross-session, local-first memory for AI agents, storing memories as Markdown files with SQLite indexing for hybrid search.
      24
      Apache 2.0

    • Engram

      rwnalds
      A
      license
      A
      quality
      A
      maintenance
      A self-hosted MCP server that gives AI agents shared, long-term memory over a git-backed folder of markdown, enabling persistent knowledge search, read, and write without a database.
      16
      14 npm
      11
      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.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a clear, distinct operation: search, direct read, graph traversal, capture, update, recent logs, status, rebuild, audit, and evaluation. There is minimal overlap between these functions, and the descriptions make boundaries obvious.

    Naming Consistency4/5

    All tools share the 'memory_' prefix and use snake_case, but the second part varies: most are verbs (search, get, capture, update, rebuild, audit, eval), while 'related', 'recent', and 'status' are not standard verb forms. This is a minor deviation from a fully uniform verb_noun pattern.

    Tool Count5/5

    With 10 tools, the server is well-scoped for a memory/knowledge management system. Each tool serves a distinct purpose from retrieval to maintenance to quality evaluation, and the count is within the ideal range for usability.

    Completeness4/5

    The server covers read, search, traverse, create, update, maintenance, and evaluation. The only obvious gap is a delete/removal operation, which may be intentionally omitted for safe memory management, but it is a minor missing capability.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources