Repository navigation
v0.3.0
Summary
0.3.0 adds poll mode: MCP clients that can't receive webhooks, or don't support MCP Events yet, can now get events from the bridge by polling. Clients that implement MCP Events poll mode call events/poll; any other MCP client, such as Claude Code, Codex or Cursor, uses the new wait_for_event and poll_events tools. Nothing to change in your config: upgrade, restart serve (or redeploy), and add the bridge to your agent as an HTTP MCP server (Claude Code: see the guide).
Added
- Poll mode (#26):
events/poll, for clients that can't receive webhooks, answered from Event Gateway's request history with no event store in the bridge.events/listofferspoll. See Polling. poll_eventsandwait_for_eventtools, the same polling for MCP clients without MCP Events support, such as Claude Code:wait_for_eventreturns as soon as there are events, or after up to 50 seconds.
Fixed
- GitHub: switching from manual mode to automatic registration no longer deletes the webhooks
setupjust created. The old registration was removed by source URL, which the new webhooks share.
Changed
- The capability is also advertised as
extensions["io.modelcontextprotocol/events"], as in the MCP Events SEP (SEP-3415), alongsideevents.
Full changelog: v0.2.1...v0.3.0 · CHANGELOG.md