Related Servers

Each tool has a clearly distinct role: the sync/async pairs (consult vs consult_async, delegate vs delegate_async, review_changes vs review_changes_async), the dry-run previews, and the job-lifecycle tools (status/result/consume/cancel/list) are all well-differentiated by their descriptions. The only mildly confusable pair is codex_job_result vs codex_job_consume_result, but the delete-vs-keep distinction is spelled out explicitly.

A consistent `codex_` prefix and snake_case are used throughout, with a predictable `_async` suffix for detached variants and a coherent `codex_job_*` namespace. Minor deviation: some tools are noun phrases (codex_status, codex_models, codex_capabilities) while most others are verb_noun (codex_consult, codex_delegate, codex_review_changes), so the verb convention is not perfectly uniform.

17 tools is on the heavier side but justified by the feature matrix: three operations (consult/review/delegate) each with sync, async, and sometimes dry-run forms, plus five shared job-management tools. Each tool earns its place, though the surface is larger than a minimal integration would need.

The surface covers the full Codex-integration lifecycle: readiness/status checks, model discovery, capability introspection, three paid operations in both sync and async form, dry-run previews, and complete background-job handling (list/status/result/consume/cancel). No obvious operational gaps remain; the only caveat is that every tool is deprecated in favor of an amicus_* successor, which is a migration concern rather than a coverage gap.