Skip to main content
Glama
Brooks-Sem

Brooks Model MCP

by Brooks-Sem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Brooks Model MCP

No user-submitted related servers found.

    Related Servers

    • CLI Agent MCP

      shiharuharu
      A
      license
      A
      quality
      F
      maintenance
      Provides unified access to multiple CLI AI agents (Codex, Gemini, Claude, and OpenCode) through a single MCP interface with real-time task monitoring, enabling specialized code analysis, UI design, implementation, and prototyping workflows.
      11
      21
      MIT

    • Vox MCP

      linxule
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients like Claude Code and Cursor to use multiple AI models (Gemini, GPT, Grok, DeepSeek, Kimi, Ollama) via a unified chat tool with conversation memory.
      3
      76 PyPI
      1
      Apache 2.0

    • all-agents-mcp

      Dokkabei97
      A
      license
      B
      quality
      F
      maintenance
      Enables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.
      14
      17 npm
      14
      MIT
    • kagero by niwa-labs

      kageroofficial

      niwa-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables unified access to multiple coding-agent CLIs via MCP, with tools for running prompts, managing sessions, and retrieving task outputs.
      MIT
    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

    A3.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: codex starts a new conversation and returns a thread ID, while codex_reply continues an existing conversation using that ID. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Both tools use lowercase snake_case and share the 'codex' prefix, making them predictable. However, one is a bare noun and the other is a noun-reply compound, so the naming pattern is not strictly verb_noun, though it remains consistent in style.

    Tool Count3/5

    With only two tools, the server sits at the thin end of the scale. For a focused Codex conversation interface, start and reply are the core operations, so the count is reasonable for the narrow purpose, but it feels minimal.

    Completeness4/5

    The core conversation lifecycle—initiate and continue—is fully covered, which is the primary use case. Missing capabilities like listing or ending threads are minor gaps that agents can work around.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources