No user-submitted related servers found.
Scored across 4 tools
Each tool has a distinct role: codex starts a new task, codex-reply continues an existing thread, codex-sessions lists recoverable threads, and codex-status reports health. The only potential confusion is between codex and codex-reply, but the descriptions make the new-vs-continue boundary clear.
Names use a consistent codex-prefixed namespace: codex, codex-reply, codex-sessions, codex-status. The bare 'codex' tool does not follow the same suffix pattern as the others, but it reads naturally as the primary action and the overall convention is predictable.
Four tools is well-scoped for a Codex bridge: one to start work, one to continue work, one to recover sessions, and one to diagnose the environment. Each tool earns its place without redundancy.
The surface covers the core lifecycle: start a task, continue a thread, list recoverable sessions, and check status. There is no explicit cancel/abort or delete-session tool, which are minor gaps an agent can generally work around.