The workflow MCP server

Edit a workflow node by node from an MCP client connected to the app's own server, or from an agent inside a workflow with the NoClick node.

NoClick's app has an MCP server of its own, at:

POST https://api.noclick.io/mcp

Connections made to it before the platform's server keep working. Where the platform's workflows_save has NoClick's builder build a workflow from a description, this server's tools edit a workflow node by node: add nodes, set their operations and fields, wire them, run them and read what each one returned. Agents inside your workflows get the same tools from the NoClick node.

New connections from Claude, ChatGPT, Cursor and the rest should use https://mcp.noclick.com, which covers workflows and everything else on the platform.

Connect a client

The server speaks Streamable HTTP and signs in with OAuth: the first time a client uses it, your browser opens on NoClick to approve the connection, and the client keeps the token. In Claude Code:

claude mcp add --transport http noclick-workflows https://api.noclick.io/mcp

Then run /mcp to sign in. Every other client takes the URL the same way it takes the platform's (Other clients), and the same troubleshooting applies.

The tools

Workflows

Tool	What it does
`list_workflows`	Lists your workflows with id, name, description and timestamps
`create_workflow`	Creates an empty workflow
`get_workflow`	Reads a workflow in full: its nodes, edges and configs
`update_workflow_metadata`	Renames a workflow or changes its description
`delete_workflow`	Deletes a workflow for good
`save_template_draft`	Saves a template's title and description to iterate on before publishing it
`get_current_workflow`	Reads the workflow open in your browser
`open_workflow`	Opens a workflow in your browser

Checkpoints

Tool	What it does
`create_checkpoint`	Saves the workflow as a named checkpoint before a risky batch of edits
`list_checkpoints`	Lists a workflow's checkpoints, newest first
`restore_checkpoint`	Restores a workflow to a checkpoint

Nodes

Tool	What it does
`get_available_node_types`	Lists the node types, optionally filtered by a search
`search_operations`	Finds operations across node types by intent, such as "post to Slack"
`get_node_operations`	Lists every operation of a node type
`get_node_configs`	Returns the config schema of node type and operation pairs
`update_workflow`	Adds, configures and connects nodes in one batch of XML edits
`validate_workflow`	Checks a workflow for build errors without running it
`autofill_node`	Fills in a node's operation and config with NoClick's builder
`get_node`	Reads one node's config and output without loading the whole workflow
`get_selected_node`	Reads the node selected in your browser
`load_value`	Reads a node's computed field values that aren't stored in its config

Runs

Tool	What it does
`run_workflow`	Runs a workflow and returns the run's id
`run_nodes`	Runs chosen nodes for testing, with the nodes before them answering from their last output
`get_execution_status`	Reads a run's status
`list_executions`	Lists a workflow's recent runs with status, trigger and timing
`get_node_output`	Reads a node's output, the latest or a past run's
`get_node_output_history`	Reads a node's last outputs across runs
`get_node_statuses`	Reads each node's latest status and error, as the canvas shows them
`list_tool_calls`	Lists the tool calls agents made during a run

Connections

Tool	What it does
`search_credentials`	Finds your connected accounts, to attach to nodes that need one
`connect_credential`	Returns the link a person opens to connect an account, by OAuth or a key
`list_credential_requests`	Reads what became of the links `connect_credential` made
`load_options`	Loads a field's options, such as your spreadsheets, sheets or channels
`credential_operations`	Lists what a connected account can do, without a workflow
`call_credential_operation`	Runs one of those operations with the account
`lookup_credential_options`	Resolves the ids an operation's fields take
`require_credential_approval`	Makes chosen operations on an account wait for its owner's approval

Workspace

Tool	What it does
`get_workflow_folders`	Reads the folder tree
`update_folders`	Creates, renames, moves and deletes folders in one batch
`list_workspaces`	Lists your personal and team workspaces, and which is active
`switch_workspace`	Switches the workspace the tools act in

Interfaces

Tool	What it does
`update_interface`	Arranges an interface's blocks on its 12-column grid
`eval_interface`	Runs JavaScript in an interface's frame, to click, type or read the page
`validate_interface`	Checks an interface's React component without opening it
`get_console_logs`	Reads recent console output from interfaces
`get_sdk_logs`	Reads recent SDK calls from interfaces, with results, errors and timing

Skills, health and feedback

Tool	What it does
`list_skills`	Lists the reusable building blocks (reference workflows and guidance) you can load
`load_skill`	Loads a skill's guidance and reference workflow
`get_health`	Checks that the server reaches its database and can run workflows
`report_bug`	Reports a bug met while building or running a workflow
`request_feature`	Asks for a missing capability

get_current_workflow, get_selected_node and open_workflow act on your browser, so they need a NoClick tab open.

The NoClick node

The NoClick node gives an agent inside a workflow these same tools, to build, change and run workflows itself. Add a NoClick node and wire it into the agent's bottom handle, as you wire any tool. It works with every agent, the CLI ones (Claude Code, Codex, OpenCode and the rest) included, and needs no connection: each run signs the agent in as you for that run. The agent sees the tools with a noclick_ prefix, such as noclick_update_workflow.

Its Scope decides which workflows the agent can touch:

Scope	What the agent gets
All workflows	Every tool, across your workspace
This workflow only	The tools, limited to the workflow the agent runs in
Specific workflows	The tools, limited to the workflows you pick under Allowed Workflows

A scoped agent gets no tools that create, list or delete workflows or manage folders and workspaces, and its workflow_id arguments are filled in for it, so it can't reach outside its scope. The tools that act on your browser are never included. The agent acts as you: with All workflows it can change or delete any workflow in your workspace, so scope it down when it only needs to manage itself.