Workflow editing via MCP/API

Hi guys. Roadmap for workflow editing via MCP or API?

I do a lot of workflow maintenance with Claude, and right now the only way to edit (I believe) is to do it via the GUI. Wondering if there’s a roadmap for at least reading workflow JSON data via MCP or API? Either would work, best if both is present.

Summary

Asking whether there is a roadmap for reading or editing Retool Workflow definitions (JSON) programmatically via MCP or the API, since editing currently appears possible only through the GUI.

AI Response

There is a Retool REST API for workflows, but the publicly documented endpoints cover operations like listing, triggering, and deleting workflows (e.g. DELETE /api/v2/workflows/{workflowId} with the workflows:write scope) rather than reading or editing a workflow's underlying definition/JSON. Retool's MCP server likewise focuses on app building, organization/user management, resource queries, and audit logs, and does not currently expose workflow-editing tools; note that the MCP resource used inside workflows is a separate feature for connecting third-party tools. For now, the supported way to move a workflow definition around is the GUI's Export/Import from JSON, though bulk updates via that path have known rough edges. No public roadmap commitment for programmatic workflow-definition editing was found in the docs or forum.

Sources

:bookmark: Delete workflows with the Retool API
Retool Team announcement confirming a workflows REST API endpoint (DELETE /api/v2/workflows/{workflowId}) and the workflows:write scope, indicating current API coverage is management operations, not definition editing.
:bookmark: Updating a Workflow using Import from JSON fails
Discusses updating a workflow via GUI Import from JSON, corroborating that JSON import/export is the present mechanism for editing workflow definitions and its current limitations.

The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a :heart:, :+1:, or :-1:. Or by marking this post as the "Solution"! Let us know if you have any feedback here. :rocket: