Skip to main content
Glama

Related Servers

Alternatives to superpower-codex-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Codex or Claude Code to orchestrate persistent Antigravity CLI workers as independent implementers and testers within restricted workspace roots. It supports asynchronous task dispatch, progress polling, result inspection, follow-up messages, and cancellation with bounded, audited local event logging.
      551 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables an automated development loop where Google Antigravity IDE performs code generation and fixes while OpenAI Codex CLI acts as an independent QA auditor, with live dashboards, slash commands, and closed-loop remediation.
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables a local Codex chat to ask a second opinion, review staged, unstaged, or revision-based diffs, and delegate coding tasks to the Antigravity CLI running in isolated or disposable workspaces. Supports starting, polling, retrieving, and cancelling tasks with returned answers, diffs, changed-file lists, exit codes, and time/output limits, while never auto-applying returned patches.
      8
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clear, distinct responsibilities: planning, review, debugging, verification, static analysis, and coding execution are separated cleanly. The only real ambiguity comes from run_gemini_coding_task being a deprecated alias of run_antigravity_coding_task, though this is explicitly documented.

    Naming Consistency5/5

    All tool names follow a consistent lowercase snake_case verb_phrase pattern, and the repeated with_codex suffix signals which actions invoke Codex. The naming is predictable and scannable, with no mixed casing or irregular verb styles.

    Tool Count5/5

    Ten tools is well within the appropriate range for a workflow-oriented MCP server. Each tool maps to a distinct workflow stage or support function, and the deprecated compatibility alias is not enough to make the set feel bloated.

    Completeness5/5

    The tool surface covers the full development loop: workspace validation, context loading, planning, static analysis, LLM review, debugging, verification, and coding execution. The orchestration tool additionally ties these stages together, so there are no significant dead ends or missing lifecycle operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues