MCP with Pulse
Pulse exposes selected topologies as tools over the Model Context Protocol (MCP). It turns Orchesty into a dynamic MCP server: an AI agent (or the built-in Pulse chat) lists the tools it is allowed to use, calls one with arguments, and Orchesty runs the matching topology and returns the result.
Pulse is not a standalone chatbot. Every request runs through the same integration engine that powers your workflows, so you keep one authorization model, deterministic execution, and full audit history.
Pulse is available on all Pro plans and Enterprise. It is not available on Starter or Community Edition.
Two ways to use Pulse #
| Track | Audience | Authentication | Docs |
|---|---|---|---|
| MCP API | External AI agents | Static API key (X-Auth) bound to an agent user | For agents |
| Pulse chat | Your logged-in users | The signed-in user's session | For your team |
Both tracks share one MCP engine. A topology you expose becomes available to whichever surface the caller's group is permitted to use.
What Pulse gives you #
- Authorization first. A caller only ever sees the topologies its group is allowed to run. The same per-user run check that guards
POST /api/topologies/{id}/runbuilds the MCP manifest, so a tool that is not in your manifest is never executed, even by an exact guessed name. - Deterministic processes. The agent picks a tool; the topology decides how it runs. Critical operations execute as defined workflows, not improvisation.
- Big-data friendly. Move and aggregate large volumes inside the topology and return a clean result, instead of streaming raw data back through the agent.
- One system authorization. Topologies run under the system identity, so the credentials your connectors use are installed once and shared, while each caller stays scoped to its own permitted processes.
How a Pulse call flows #
The caller lists tools #
An agent fetches the manifest from GET /mcp/manifest.json, or the Pulse chat loads the same manifest for the signed-in user. The manifest contains only the tools the caller is authorized to use.
The caller runs a tool #
The caller sends POST /mcp/run with a tool id and arguments. Orchesty re-checks the run ACL, validates the arguments against the tool's input_schema, and starts the topology.
Orchesty returns the result #
A command topology is fire-and-forget. A query topology returns its payload through a response node once the process finishes.
Where to go next #
- Getting started with Pulse: expose your first topology as a tool.
- For agents: the MCP API, manifest, and run endpoint.
- For your team: the built-in Pulse chat.