Skip to main content
Glama
jgt87
by jgt87

Related Servers

Alternatives to codex-offload-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A4.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: starting tasks (codex_start, codex_execute_plan), checking status (codex_status), collecting results (codex_result), canceling (codex_cancel), replying (codex_reply), listing models (codex_models), and listing jobs (codex_list). No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent 'codex_' prefix followed by a clear verb or verb_noun pattern (start, execute_plan, status, result, cancel, reply, models, list), maintaining perfect naming consistency.

    Tool Count5/5

    8 tools is well-scoped for managing background Codex jobs: covering task initiation (two variants for different workflows), monitoring, result collection, cancellation, follow-up, model discovery, and job listing. No superfluous or missing tools.

    Completeness5/5

    The tool surface covers the full lifecycle of background job offloading: start (with plan variant), status, result, cancel, reply, list, and model queries. No obvious gaps for the intended domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues