Pick up where you left off
Events are stored before receipt is acknowledged. Reconnect to replay pending deliveries, with stable IDs and local deduplication.
Connect MCP Events to the agent sessions where you work. A durable relay keeps messages moving—even when your machine is offline.
Codex first. Any compatible MCP Events source.
Transport that stays out of your agent’s way.
Events are stored before receipt is acknowledged. Reconnect to replay pending deliveries, with stable IDs and local deduplication.
Watch multiple sources and events. Assign each subscription to a session with its own standing instructions, managed through MCP tools.
Your upstream MCP credentials stay on your machine. Dedicated environment identities authenticate the connection; the relay holds webhook verification secrets.
Run the Worker locally, enroll an environment, and start the CLI daemon. Add its MCP tools to Codex to discover events and subscribe from your conversation.
Read the complete setup guide ↗# Node 22.13+ · npm git clone https://github.com/polvi-ish/mcp-events-relay cd mcp-events-relay npm ci cp .dev.vars.example .dev.vars npm run dev # In another terminal, after enrollment npm run cli -- daemon # Register the MCP control interface codex mcp add mcp-events-relay -- node \ "$PWD/dist/relay.mjs" mcp
codex queue. Pending events are retained for
seven days.Compatibility & limitations ↗