feat: Expose workflow authoring and control through MCP #323

New issue

Closed

opened 2026-07-13 19:46:13 +02:00 by dries · 0 comments

dries commented

2026-07-13 19:46:13 +02:00

Owner

Parent

#311

What to build

Give coding agents a compact MCP surface for validating/publishing workflow definitions and controlling workflow runs through the same service used by REST and the UI.

Acceptance criteria

MCP tools validate and publish definitions without duplicating workflow business logic.
Agents can list workflow definitions/versions and start a pinned or active version.
Agents can list and inspect runs, nodes, attempts, and compact artifact metadata.
Agents can pause, resume, cancel, approve waiting nodes, and resolve unknown attempts.
Tool responses expose stable IDs, concise state, and actionable validation errors.
Tool descriptions remain short; orchestration guidance lives in a repository skill/document.
Tools enforce the existing localhost/auth boundary and never return secret values.
Existing loop tools remain unchanged until the compatibility migration ticket.
Contract tests prove MCP and REST produce equivalent service behavior.

Blocked by

#313

## Parent #311 ## What to build Give coding agents a compact MCP surface for validating/publishing workflow definitions and controlling workflow runs through the same service used by REST and the UI. ## Acceptance criteria - [ ] MCP tools validate and publish definitions without duplicating workflow business logic. - [ ] Agents can list workflow definitions/versions and start a pinned or active version. - [ ] Agents can list and inspect runs, nodes, attempts, and compact artifact metadata. - [ ] Agents can pause, resume, cancel, approve waiting nodes, and resolve unknown attempts. - [ ] Tool responses expose stable IDs, concise state, and actionable validation errors. - [ ] Tool descriptions remain short; orchestration guidance lives in a repository skill/document. - [ ] Tools enforce the existing localhost/auth boundary and never return secret values. - [ ] Existing loop tools remain unchanged until the compatibility migration ticket. - [ ] Contract tests prove MCP and REST produce equivalent service behavior. ## Blocked by - #313