Skip to main content
Glama
3lehr

brainlehr

by 3lehr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to brainlehr

No user-submitted related servers found.

    Related Servers

    • local-rag-mcp

      Orax0001
      A
      license
      Not graded
      quality
      C
      maintenance
      A privacy-preserving local RAG system integrated with MCP, enabling natural language queries over ingested documents and a SQLite database through vector search and local database tools.
      MIT

    • Argon Memory

      Tangtaizong-BUAA
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP agents to maintain durable, evidence-aware project knowledge, retrieve precise excerpts on demand, and track decisions, conflicts, and revisions across sessions.
      1
      Apache 2.0

    • tugra

      dogrucanemek-alt
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to store and retrieve provenance-aware facts with source, age, and boundaries, supporting search, read, propose, and local telemetry via MCP tools.
      4
      69 npm
      Apache 2.0

    • Talamus

      ampres-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first, source-grounded memory for AI agents, with citations, bitemporal history, review-gated corrections, and MCP tools for search and recall.
      3
      Apache 2.0

    • fortytwo-guide

      justfortytwo
      A
      license
      Not graded
      quality
      B
      maintenance
      A semantic-memory MCP server that stores text 'memories' with provenance and enables recall by meaning (vector search), keyword (FTS5), or structured filters.
      185 npm
      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

    B3.1/5.0

    Scored across 45 tools

    Disambiguation3/5

    Most tools fall into recognizable domain clusters (knowledge_*, lesson_*, project_*, session_*, annahme_*), and the detailed descriptions often explicitly separate near-neighbors. However, several abstract project-lifecycle tools (project_boundary, project_actor_boundary, project_commit_gate, project_runtime_evidence, project_commit_ack, project_change) are hard to distinguish by name alone, and freigabe_setzen vs. knowledge_freigeben use overlapping 'release' vocabulary for different operations.

    Naming Consistency3/5

    The server uses useful prefixes like knowledge_, project_, session_, and lesson_, but mixes English verbs (knowledge_add, lesson_record) with German verbs (knowledge_zurueckziehen, session_checkpoint_setzen) and inconsistent noun/verb structures (annahme_liste, freigabe_setzen, knowledge_trust_score). The pattern is readable but not predictable enough for an agent to guess tool names reliably.

    Tool Count2/5

    45 tools is far above the well-scoped 3-15 range and even above the 16-25 'heavy' band. While the overall domain is broad and each tool seems specialized, the surface would be much more navigable if project lifecycle/evidence tooling and knowledge statistics/reporting were consolidated or split into separate sub-servers.

    Completeness4/5

    The knowledge tree, relations, lessons, assumptions, sessions, project evidence, and setup each have reasonable lifecycle coverage, including nuanced operations like withdrawal, re-release, trust scoring, and curator runs. The main gaps are minor but real: no way to update an assumption after creation, no node move/reparent operation, and no catalog removal tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources