workflows

Files and workflowsFull

The user's saved workflows: the steps they set up to run after a capture (copy it to a folder, rename it, export or share it). An agent lists them and runs one on an item; making or changing them is the user's, in the Workflows window.

Needs the Full level, which is the default for any client holding the bearer token.

Parameters

Name	Type	Required	Description
action	string one of "list", "run"	yes	What to do. list: The user's saved workflows: id, name, on or off, what triggers each, its steps (tool and action), and whether agents may run it without asking. run: Run a saved workflow on an item (id or path, default the gallery's current item), as the Workflows window's Run now does: every step, whatever its trigger. The user is asked first, unless they let agents run that workflow without asking. (workflow, id, path)
workflow	string	no	run: the workflow's id or name, from list.
id	string	no	run: the item to run it on (default the gallery's current item).
path	string	no	run: or the item's path or name.

Example

A JSON-RPC call to POST http://localhost:21516/mcp with the bearer token, filling in the required parameters:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "workflows",
    "arguments": {
      "action": "list"
    }
  }
}

See the MCP server overview for how to connect a client and where the token lives.