Support and tickets
When a new issue, status change, or escalation enters a topic, the agent can reply, classify, or hand it off.
Event-driven AI agents
The official MsgMesh MCP Server turns the event bus into tools an agent can call. The agent waits with watch_topic, handles an event, then waits again.
Where it fits
Schedules fit work at a known time. Event subscriptions fit work that must start whenever something happens.
When a new issue, status change, or escalation enters a topic, the agent can reply, classify, or hand it off.
Send actionable business alerts into a stream so an agent can gather context and propose the next step.
When an order, refund, or review result arrives, the agent can call the next tool while your system owns the write.
How it works
Your service publishes a JSON event to an existing topic over HTTP or an SDK. MsgMesh does not interpret the payload.
The tool long-polls for the next batch. It reads the whole topic and cannot filter by room.
The MCP client gives the event to the model. Your agent host and prompt policy decide whether execution is automatic or requires approval.
Keep the watch → react → watch loop bounded. Record cursors and outcomes so failures do not cause endless repeats.
Permissions and safety
| Need | Recommended key | Why |
|---|---|---|
| Wait for events only | Consumer key or subscribe-only capability key | A leaked key cannot publish or manage resources. |
| Receive events and publish results | Subscribe + publish only on selected topics | Keep reads and writes inside the agent's workflow. |
| Create topics or keys | Admin key | Governance tools need admin scope; keep them out of uncontrolled loops. |
Keep reading
MCP setup takes about five minutes. Keep human approval on governance tools.