No user-submitted related servers found.
Scored across 10 tools
Each tool targets a distinct part of the bridge workflow—submitting, receiving, answering, cancelling, steering, session management, artifacts, projects, diagnostics. The only mild concern is bridge_submit and bridge_steer both relate to continuing or picking up sessions, but the descriptions clarify that steer adopts existing queue items without enqueueing.
All tools share a consistent bridge_ prefix, which aids discoverability, but the action part mixes noun-style names (bridge_projects, bridge_receipt, bridge_sessions) with verb-style names (bridge_answer, bridge_cancel, bridge_submit, bridge_steer) and one compound (bridge_session_manage). This mixed convention is readable but not a uniform verb_noun pattern.
With 10 tools, the server is well within the ideal range and each tool covers a distinct capability needed for the bridge domain. No tool feels redundant, and the count is appropriate for the scope.
The surface covers the full session lifecycle: submit/continue, answer clarifications, poll receipts, cancel, recover/adopt queue items, and manage sessions. Project aliases, artifacts, and diagnostics round out the supporting needs, so agents are unlikely to hit obvious dead ends.