Skip to main content

Crate odori_mcp_bridge

Crate odori_mcp_bridge 

Source
Expand description

The MCP bridge — durable tools reachable from inside a harness turn.

A harness (Claude Code, Codex) mid-turn may call a tool the framework owns. That tool must execute durably — as a tokeira activity with its own retry policy — while the harness blocks awaiting the MCP response, inside a turn that is itself an activity. This crate is that bridge:

  • attach::Bridge — the in-process streamable-HTTP MCP server on loopback, per-attempt bearer tokens, and the AttachmentSource implementation the turn activities consume;
  • broker::CallBroker — tools/call → workflow update translation with keepalive progress (record-before-respond is structural: only a completed update’s reply can be returned);
  • the workflow-side pieces (invocation registry, tool_invoked update handler, execute_tool activity) live in odori-agents, which this crate depends on — never the reverse.

The preview feature gates the complete bridge: with it off this crate compiles to nothing — no listener, no attachment, no bridge code on any path — and framework tools delegate to the harness’s own tooling. (Module references above are plain code spans, not links: the modules exist only under preview, and the preview-off rustdoc build must stay warning-free.)