Skip to main content
Glama
QEbellavita

system-brain-mcp

by QEbellavita
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to system-brain-mcp

No user-submitted related servers found.

    Related Servers

    • depot-mcp

      akshayjain3450
      F
      license
      A
      quality
      A
      maintenance
      Provides coding agents read-only access to Depot's CI failure diagnoses, container build forensics, run history, cache effectiveness, registry contents, and usage data through MCP tools.
      28
      49 npm
      1
      -

    • OPP Observatory MCP

      OPP-studio-macchino
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only production observability through a small set of tools for health, job status, latest data, approved logs, and deployment metadata, enabling AI planning and review without a production write path.
      MIT

    • saas-audit-mcp

      THE-KIPDEV
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to audit a Next.js codebase read-only, checking routes, Prisma models, environment variables, and locale consistency via MCP tools.
      MIT

    • Zendesk MCP Server

      rlowndes9
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to audit and analyze Zendesk instances through a read-only MCP interface, providing tools for triggers, automations, analytics, and cross-reference queries.
      74
      MIT

    • MCQuest MCP

      LionTechSupport
      F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that gives AI coding agents structured access to a project's source code, architecture, documentation, and Git context through 16 tools for searching, reading, and comparing evidence without modifying files.
      16
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: deploys, backlog, DB schema, ML models, analytics, architecture docs, fabrication audit, lenses, roadmap, recommend, and reframe. Descriptions clearly separate related tools like db_schema vs. analytics and backlog vs. roadmap.

    Naming Consistency4/5

    All tools share the 'brain_' prefix, creating a clear family, but the suffixes mix nouns (backlog, analytics, architecture), verbs (recommend, reframe), and query-like phrases (where_deploys). This is mostly consistent but not a strict verb_noun pattern.

    Tool Count5/5

    11 tools is well within the ideal range for a decision-support brain. Each tool covers a discrete capability needed for the apparent domain, and none feel redundant or superfluous.

    Completeness4/5

    The tool surface covers the full gather-analyze-recommend-reframe loop using available evidence sources. Minor gaps exist—e.g., no direct GitHub issue/PR detail lookup beyond the backlog aggregate, and no tool for explicit doc searches—but agents can work around these.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources