What the MCP server can do

Connect the server first — see Install the MCP server.

Context and docs

Tool	What it does
`getContext`	Returns your user context, including organization IDs and names. Call it first — most tools need an organization UUID.
`searchDocs`	Searches these docs.

Workflows and profiles

Tool	What it does
`agentList`	Lists the workflows in an organization.
`agentCreate`	Creates a workflow with its first graph, and publishes that graph as version 1.
`agentRename`	Renames a workflow. The name takes 1 to 100 characters.
`agentDelete`	Deletes a workflow and its versions. Every execution must be terminal first.
`agentProfilesList`	Lists the agent profiles in an organization.
`agentProfilesCreate`	Creates a profile.
`agentProfileGet`	Reads one profile.
`agentProfileUpdate`	Changes a profile.
`agentProfileDelete`	Deletes a profile.
`agentProfileClearBrowserCache`	Clears the browser state a profile has kept.

Executions

Tool	What it does
`agentExecutePost`	Starts an execution of the published version.
`executionsList`	Lists runs, with filters and pagination.
`executionGet`	Returns everything about one execution.
`executionView`	Draws an execution viewer in the chat, with status, activity, and result.
`executionActivitiesGet`	Returns the timeline of tool calls, messages, and events.
`executionAgentFilesGet`	Lists the files an execution produced, grouped by directory.
`executionContextFilesGet`	Lists the files attached to an execution.
`executionStatusUpdate`	Pauses, resumes, or cancels an execution.
`executionUserMessagesAdd`	Sends a message to a running workflow.

Executions and statuses lists the statuses these tools return. Debug your workflows covers how to read a failure.

Versions

Tool	What it does
`workflowsList`	Lists the versions of a workflow.
`workflowGet`	Loads one version: graph, rules, and settings.
`workflowCreate`	Creates a version. Set `parentId` to record where it came from. It stays unpublished.
`workflowPublish`	Publishes a version, so new executions use it.
`workflowExecute`	Runs one specific version, published or not. Use it to test a draft.

Files and validation

A workflow’s graph and its files are the same thing, viewed two ways. Node instructions, settings, and scripts all show up as files. Editing the editable head lands in place. Editing a published or already-executed version forks a new one instead. See Workflow filesystem for where the files land at run time.

Tool	What it does
`workflowFilesList`	Lists the agent’s editable workflow as files. Returns a `rev`, which you pass back as `baseRev` to write.
`workflowFilesListByVersion`	Lists the same files for one pinned, immutable version instead of the editable head.
`workflowFilesPatch`	Writes or deletes files on the editable workflow in one call.
`workflowAgentFileSignedUrl`	Returns a short-lived URL for reading a file.
`schemaValidate`	Checks a JSON schema before you put it on an output node.
`workflowSpecValidate`	Checks a graph before `agentCreate` creates anything.
`workflowValidate`	Runs the same check against a workflow that already exists.

Live environments

Tool	What it does
`environmentStart`	Starts a standalone environment and returns its connection details, including a proxied CDP URL.
`environmentsList`	Lists an organization’s currently-running standalone environments.
`environmentGet`	Reads one environment: its status and its CDP URL.
`environmentStop`	Stops a running environment.

See Live environments for how to connect to one.

Build a workflow over MCP

See these tools used together, start to finish.

Get Started

Reference

Context and docs

Workflows and profiles

Executions

Versions

Files and validation

Live environments

Next

Build a workflow over MCP

​Context and docs

​Workflows and profiles

​Executions

​Versions

​Files and validation

​Live environments

​Next

Build a workflow over MCP

Context and docs

Workflows and profiles

Executions

Versions

Files and validation

Live environments

Next