MCP events
As of v1.9.0, Outpost can be the backend for MCP Events, the draft MCP extension that lets an agent subscribe to events from your MCP server and receive them as webhooks. Your MCP server forwards events/list, events/subscribe and events/unsubscribe to Outpost, and Outpost verifies the callback URL, stores the subscription, and signs, filters and delivers each matching event.
What's new
Agents connected to your MCP server can list your event types and subscribe to one, with arguments that filter on payload fields. Outpost delivers matching events straight to the agent's callback URL, signed with Standard Webhooks. Deliveries don't pass through your MCP server.
Publishing doesn't change. One publish reaches every matching subscription for that tenant, and a tenant's topics include the events its agents subscribe to.
To try it locally, mcp-dev runs a reference MCP server, receiver and client with sample events, and mcp-dev check tests any MCP Events server against the spec.
Limitations
For now, MCP Events is experimental and off by default. Since the spec is still a draft, details such as error codes may change. Delivery is webhook mode only, matching what ChatGPT supports: there's no poll or streaming delivery and no cursor replay.