MCP Events for Business: From a New Request to Agent Work

A new request can trigger document collection and a draft handling plan before someone opens the inbox. That workflow needs both a notification and tools to perform the work. MCP Events concern events from connected applications that an automation can respond to.

On 29 September 2026, OpenAI announced support for the proposed MCP Events specification in plugin automations. Its example starts with a new project-board task and prepares a plan from linked documents. Checked on 1 October 2026. OpenAI announcement.

Distinguish events, tools and schedules

A tool exposes an operation, such as reading a request. An event reports a change, such as its creation. A schedule starts work at a specified time. One process may use all three.

MCP support does not establish MCP Events support. Check the specific plugin, client and connection. The proposed specification also needs to be tracked as it develops. Do not assume that any MCP server can already send events to every assistant.

A service-desk example

This is a proposed implementation. An event provides the request identifier, and the integration retrieves its current state. The agent checks approved documentation and prepares a reply draft. If an order number is missing, it records a question for the operator. The result goes into a review queue.

Beyond the model instruction, the workflow needs a restricted account, a trigger rule, an output location and execution state. It also needs a way to stop or resume work after failure.

Sending the reply can remain with the employee. Automating that step later requires its own rules, permissions and trials.

Handle repeated events

Check the delivery guarantees of the integration. Do not assume events always arrive once and in order. A repeated notification should not generate a second quote or resend a message.

A custom execution layer can keep an operation record tied to the business case, action and source version. It checks that record before writing. Implement and verify this record in the integration layer; MCP Events support alone does not provide it.

If a write succeeded but its acknowledgement was lost, inspect the destination system first. Blind retries are particularly problematic for financial actions. Send uncertain cases to an operator with the identifier and attempt history.

Keep data separate from authority

The request's text is input to the process. It should not expand the agent's access. An account reading orders needs the scope approved by the business. Expose write tools for specific operations.

Ada Computer illustrates a related direction by combining API, MCP and code tools. Monetary rules and permissions can be implemented in application code and business systems. The vendor presents its examples as demonstrations. Ada Computer.

Cost and acceptance

Monthly cost includes executions, models, tools, state storage and exception handling. If 10% of 1,000 cases need a second attempt, there are 1,100 attempts. This is a calculation example; context length and tool execution also affect the bill.

Syntalith automations start at €1,750 excluding VAT, while apps and agents start at €3,000 excluding VAT. The scope of decisions and integrations determines the appropriate service. Running costs and maintenance are separate.

At acceptance, test an ordinary request, a duplicate, missing access and interruption after a write. Describe the event that starts your process. See the quote-preparation example for a specific workflow, or Team Tasks for scheduled reports.