> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noclick.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Available MCP Tools

> All 47 tools exposed by the NoClick MCP server

When you connect the NoClick MCP server to an AI assistant, it gets 47 tools for building, running, and debugging workflows. Your assistant discovers how to use each tool automatically. Just describe what you want to build.

## Workflows

| Tool                       | Description                                                                                   |
| -------------------------- | --------------------------------------------------------------------------------------------- |
| `list_workflows`           | List your workflows with id, name, description, and timestamps                                |
| `create_workflow`          | Create a new empty workflow                                                                   |
| `get_workflow`             | Get full workflow details including all nodes, edges, and configs                             |
| `update_workflow_metadata` | Update a workflow's name and/or description                                                   |
| `delete_workflow`          | Permanently delete a workflow (irreversible)                                                  |
| `save_template_draft`      | Save a template title and description to iterate on before publishing to the template library |
| `get_current_workflow`     | Get the workflow currently open in your browser                                               |
| `open_workflow`            | Open a workflow in your browser                                                               |

## Checkpoints

| Tool                 | Description                                                                       |
| -------------------- | --------------------------------------------------------------------------------- |
| `create_checkpoint`  | Snapshot the current workflow as a named checkpoint before a risky batch of edits |
| `list_checkpoints`   | List a workflow's saved checkpoints, newest first                                 |
| `restore_checkpoint` | Restore a workflow to a saved checkpoint (irreversible)                           |

## Nodes

| Tool                       | Description                                                                     |
| -------------------------- | ------------------------------------------------------------------------------- |
| `get_available_node_types` | List all available node types, with optional search filtering                   |
| `search_operations`        | Search operations across node types by intent, such as "post to Slack"          |
| `get_node_operations`      | Enumerate all operations of a known node type                                   |
| `get_node_configs`         | Get config schemas for node type and operation pairs                            |
| `update_workflow`          | Add, configure, and connect nodes in one batch of XML mutations                 |
| `validate_workflow`        | Check a workflow for build errors without running it                            |
| `autofill_node`            | Auto-fill a node's operation and config using the internal builder engine       |
| `get_node`                 | Get a single node's configuration and output without loading the whole workflow |
| `get_selected_node`        | Get the node currently selected in your browser                                 |
| `load_value`               | Fetch a node's live computed field values that are not stored in its config     |

## Execution

| Tool                      | Description                                                                       |
| ------------------------- | --------------------------------------------------------------------------------- |
| `run_workflow`            | Execute a workflow, returns an execution id                                       |
| `run_nodes`               | Run specific nodes for testing, with upstream nodes mocked from their last output |
| `get_execution_status`    | Check the status of a workflow execution                                          |
| `list_executions`         | List recent runs of a workflow with status, trigger source, and timing            |
| `get_node_output`         | Get node outputs, the latest by default or a specific past run by execution id    |
| `get_node_output_history` | Get the last outputs of a single node across executions                           |
| `get_node_statuses`       | Get the latest status and error per node, the same chips shown on the canvas      |
| `list_tool_calls`         | List the agent tool calls made during a workflow execution                        |

## Credentials

| Tool                       | Description                                                                     |
| -------------------------- | ------------------------------------------------------------------------------- |
| `search_credentials`       | Search your saved credentials for configuring nodes that need authentication    |
| `connect_credential`       | Mint a link the user opens to connect a credential (OAuth or API key)           |
| `list_credential_requests` | Poll the status of connect\_credential requests you've minted                   |
| `load_options`             | Load dynamic dropdown options for a node field (spreadsheets, sheets, channels) |

## Workspace

| Tool                   | Description                                                            |
| ---------------------- | ---------------------------------------------------------------------- |
| `get_workflow_folders` | Get the folder tree for organizing workflows                           |
| `update_folders`       | Batch folder mutations (create, rename, move, delete) via XML commands |
| `list_workspaces`      | List your personal and organization workspaces and which is active     |
| `switch_workspace`     | Switch between personal and organization workspaces                    |

## Interface

| Tool                 | Description                                                                                          |
| -------------------- | ---------------------------------------------------------------------------------------------------- |
| `update_interface`   | Position and arrange interface blocks on the 12-column grid layout                                   |
| `eval_interface`     | Evaluate a JavaScript expression inside an interface node's iframe to click, type, or read DOM state |
| `validate_interface` | Validate an interface node's JSX/React component headlessly                                          |

## Skills

| Tool          | Description                                                                       |
| ------------- | --------------------------------------------------------------------------------- |
| `list_skills` | List the reusable building blocks (reference workflows and guidance) you can load |
| `load_skill`  | Load a skill's full guidance and reference workflow                               |

## Debugging

| Tool               | Description                                                                      |
| ------------------ | -------------------------------------------------------------------------------- |
| `get_console_logs` | Get recent console output from interface node iframes                            |
| `get_sdk_logs`     | Get recent SDK call logs from interface iframes (calls, results, errors, timing) |
| `get_health`       | Self-test the MCP server's database and execution connectivity                   |

## Feedback

| Tool              | Description                                                   |
| ----------------- | ------------------------------------------------------------- |
| `report_bug`      | Report a bug encountered while building or running a workflow |
| `request_feature` | Request a missing capability or improvement                   |

<Note>
  `get_current_workflow`, `get_selected_node`, and `open_workflow` interact with your live browser session, so they need a NoClick tab open.
</Note>

## Example usage

Here is how a typical build looks with the NoClick MCP server connected:

<CodeGroup>
  ```text Build a workflow theme={null}
  "Create a workflow that checks Hacker News RSS every hour,
  filters for AI-related posts, and sends a Slack summary"
  ```

  ```text Configure nodes theme={null}
  "Add a Perplexity node to search for today's news about
  startups and connect it to the Gmail node"
  ```

  ```text Test and run theme={null}
  "Run just the RSS node to see what data it returns,
  then run the full workflow"
  ```
</CodeGroup>

Your assistant handles the details: discovering node types, configuring operations, wiring credentials, and connecting nodes.

## Next steps

<CardGroup cols={2}>
  <Card title="Set up NoClick MCP" href="/mcp/setup">
    Connect these tools to Claude, ChatGPT, Cursor, and other clients.
  </Card>

  <Card title="NoClick node" href="/mcp/noclick-node">
    Give these same tools to agents inside your workflows.
  </Card>
</CardGroup>