Skip to main content
Glama

Related Servers

Alternatives to codex-mcp-bridge

Related Servers

TDQS

A3.9/5.0

Scored across 12 tools

Disambiguation3/5

Several tools overlap in starting and continuing Codex conversations (start_codex_thread, delegate_to_codex, send_to_codex_thread, wait_codex_reply), making it easy to misselect despite detailed descriptions. Read/list/open and inspect/prepare have clearer boundaries, but the conversation lifecycle tools are subtle.

Naming Consistency4/5

Mostly consistent snake_case with verb_noun or verb_to_noun patterns. One outlier is codex_bridge_status (noun-first), and delegate_to_codex uses an unusual 'to_codex' suffix, but the set remains readable and predictable overall.

Tool Count4/5

12 tools is reasonable for a bridge covering thread management, messaging, project authorization, and app-server lifecycle. No excessive bloat, though a few conversation tools could potentially be consolidated.

Completeness4/5

Covers listing, reading, opening, sending, interrupting, starting/stopping app-server, status, and project onboarding. Minor gaps like thread archiving or deletion exist, but core bridge workflows are well represented.

Maintenance

ActivityActive
ResponsivenessWithin a week