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
      D
      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.
      3 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.
      1 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
      6 npm
      16
      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.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct action/resource: search vs. get vs. recent logs, and a clean memory_candidate_* sub-namespace (get/list/create/approve/reject/expire) that is explicitly isolated from canonical memory. The three write paths (capture, update, candidate_create) are clearly differentiated by descriptions. No two tools appear interchangeable.

    Naming Consistency5/5

    All 16 tools use a uniform memory_ prefix in snake_case with a predictable verb_noun structure (memory_get, memory_search, memory_capture, memory_update). The memory_candidate_* lifecycle is a consistent nested naming sub-pattern rather than a deviation.

    Tool Count4/5

    16 tools is at the upper edge of comfortable, driven by a full five-tool candidate-review lifecycle. For a knowledge base with retrieval, audit, eval, and index management, each tool earns its place, though the surface is slightly heavy.

    Completeness5/5

    The surface covers the full lifecycle: creation (capture/create), read (get/search/related/recent), update (update, approve), review governance (candidate list/approve/reject/expire), plus audit, eval, rebuild, and status. Append-only design intentionally omits canonical delete, so no meaningful dead ends remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources