Skip to content

feat(agent-toolkit): add workflow-builder read tools (get_workflow / list_workflows)#433

Open
jonathanHeiss1 wants to merge 3 commits into
mondaycom:masterfrom
jonathanHeiss1:feat/workflow-builder-read-tools
Open

feat(agent-toolkit): add workflow-builder read tools (get_workflow / list_workflows)#433
jonathanHeiss1 wants to merge 3 commits into
mondaycom:masterfrom
jonathanHeiss1:feat/workflow-builder-read-tools

Conversation

@jonathanHeiss1

Copy link
Copy Markdown

Summary

Adds two read-only MCP tools that expose standalone, workspace-level workflows (Workflow Builder — distinct from board automations) through the workflow-builder subgraph on the dev GraphQL API version, following the same pattern as the existing list_automations tool and the workflow-builder-tools family (create_workflow, etc.):

  • get_workflow (READ) — fetch one or more workflows by workflow object ID, returning metadata + the ordered list of steps. IDs that don't resolve are omitted.
  • list_workflows (READ) — cursor-paginated list of the account's live (published) workflows.

Both call workflows(ids) / live_workflows_page(pagination) via mondayApi.request(..., { versionOverride: 'dev' }) and share a single read-model mapper so they return identical workflow shapes (id, title, description, active, created_at, updated_at, steps[{ node_id, block_reference_id, title }]).

Why

When a user interacts with the platform MCP there is currently no way to read a Workflow Builder workflow's definition — create/update/plan/publish_workflow exist, but no get/list. This closes that gap, mirroring how automations already have list_automations.

Notes

Test plan

  • yarn jest — 14 new unit tests pass (id→variable mapping, null filtering, pagination cursor/hasMore, versionOverride: 'dev', zod validation, error paths)
  • eslint — clean on all new/changed files
  • tsc --noEmit — no new errors (the two pre-existing TS2589 errors in src/mcp/toolkit.ts reproduce on clean master)
  • Local MCP smoke test against an account with ENABLE_EXTERNAL_WORKFLOW_GRAPHQL_API enabled

Made with Cursor

jonathanHeiss1 and others added 3 commits July 13, 2026 17:42
…ows)

Adds two read-only MCP tools that expose standalone, workspace-level
workflows (distinct from board automations) via the workflow-builder
subgraph on the dev GraphQL API version:

- get_workflow (READ) — fetch one or more workflows by object ID,
  returning metadata and ordered steps.
- list_workflows (READ) — cursor-paginated list of the account's live
  workflows.

Both reuse a shared read-model mapper so they return identical workflow
shapes, following the existing list_automations tool pattern.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant