MCP Trigger starts a Joomla or WordPress flow when an agent calls a tool on that site. One flow is one tool. The agent sends the bearer token from Node Configuration → Custom Ev…
MCP Trigger starts a Joomla or WordPress flow when an agent calls a tool on that site. One flow is one tool. The agent sends the bearer token from Node Configuration → Custom Events → MCP.
When this trigger fires, JOrchestrator starts the flow and passes the incoming event or request data to the next connected step. Configure filtering, payload shape, and security on the Design tab.
MCP Trigger is a trigger in the Custom Events group. Triggers start a flow. They listen for an external signal — a CMS event, inbound HTTP call, payment notification, or schedule — and pass the incoming data to the first downstream step.
Typical reasons teams add MCP Trigger to a flow:
This trigger starts the flow when an MCP client calls the tool on your linked Joomla or WordPress site. Downstream steps receive the tool arguments as their input.
Common patterns on the canvas:
Name the tool, describe what it does, and set the arguments later steps can use. In the site's Node Configuration → Custom Events → MCP, turn the provider on and generate a bearer token. Clients send that token as Authorization: Bearer. The MCP address is the same for every flow on the site and is shown on the Design tab.
Set JSON on this flow becomes the tool's structured result. Set Response becomes the text result. A flow failure is returned as a tool error. The tool is listed only while this flow is Active and the node is enabled.
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| General | Canvas label and read-only node ID |
| Design | Tool name, arguments, and the shared MCP address |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
_mcpEndpointUrl | MCP endpoint | mcp-endpoint-url | No | — | Clients POST JSON-RPC to this address with Authorization: Bearer set to the MCP token. One address serves every MCP Trigger on the site. |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
toolName | Tool name | text | Yes | — | Shown to MCP clients. Start with a letter. Letters, numbers, underscores, and hyphens only, up to 64 characters. Must be unique among active flows on this site. |
description | Description | textarea | No | — | Plain description sent in tools/list. Do not put secrets here. |
inputSchema | Arguments | json-schema | No | — | JSON schema for the tool arguments. Required fields are enforced when a client calls the tool. Downstream nodes can use these fields. |
outputSchema | Result schema (optional) | json-schema | No | — | Advertised on tools/list. The call still returns whatever Set JSON or Set Response writes. A mismatch does not fail the call. |
enabled | Enabled | toggle (default: true) | No | — | Turn off to hide this tool without deleting the node. |
timeoutSeconds | Timeout (seconds) | number (default: 60) | No | — | PHP time limit for the tool call, from 5 to 120 seconds. The web server limit still applies. Closing the client does not cancel the run. |
Turn the MCP provider on and generate the bearer token in the CMS plugin under Node Configuration → Custom Events → MCP. Link the flow to a domain and keep the flow Active so the tool is listed.
After this step runs, later nodes can reference these fields using placeholders such as {{mcp_trigger.toolName}}.
| Field key | Type | Description |
|---|---|---|
toolName | string | Tool name the agent called. |
| (argument fields) | mixed | Each property in Arguments is available to downstream steps under the node label. |