mcp_pipeline
mcp_pipeline
Section titled “mcp_pipeline”Category: meta
Execute a sequence of MCP tool calls in one request. Variables from earlier steps interpolate into later steps via \{\{step_id.path\}\}.
When to use
Section titled “When to use”when a workflow needs ≥2 sequential calls (e.g., list channels → find by name → send message). Reduces N round-trips to 1.
When NOT to use
Section titled “When NOT to use”parallel-safe independent calls — issue them as separate tools/call requests. Long-running batch ops — use the dedicated bulk tool (Plan 7+) so each operation can fail independently.
| Field | Type | Required | Description |
|---|---|---|---|
steps | array | yes | Ordered steps. Max 20 per pipeline. |
Returns
Section titled “Returns”\{steps:[\{id, tool, status, result?, error?, duration_ms\}], variables, total_duration_ms, aborted\}. Each step status is success | error | skipped.
Output schema
Section titled “Output schema”| Field | Type | Required | Description |
|---|---|---|---|
steps | array | yes | |
variables | object | yes | |
total_duration_ms | number | yes | |
aborted | boolean | yes |
Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | no |
| Destructive | no |
| Idempotent | no |
| Open-world | yes |
| Confirmation required | no |