> ## 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.

# Setting Up NoClick MCP

> Connect NoClick to Claude, Claude Code, ChatGPT, Cursor, Windsurf, OpenAI Codex, or any MCP-compatible AI assistant

# Setting Up NoClick MCP

NoClick provides an MCP (Model Context Protocol) server that lets you interact with your workflows directly from AI coding assistants. Create, configure, and run workflows without leaving your editor.

## What is MCP?

MCP (Model Context Protocol) is an open standard that allows AI assistants to securely connect to external tools and data sources. With NoClick MCP, your AI assistant can:

* Create, edit, and delete workflows in real time
* Add and configure nodes with full progressive disclosure
* Execute workflows and inspect results
* Manage credentials and dynamic field options

NoClick uses **OAuth 2.1 with PKCE** for authentication. Your browser opens once to authorize, and the token is saved automatically.

***

## Claude Code

<iframe width="100%" height="400" src="https://www.youtube.com/embed/o3OlH9X_8Go" title="Connect NoClick MCP to Claude Code" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen style={{ borderRadius: '8px', marginBottom: '16px' }} />

The recommended way to connect. Add NoClick to your project's `.mcp.json` file in the project root:

```json theme={null}
{
  "mcpServers": {
    "noclick": {
      "type": "http",
      "url": "https://api.noclick.io/mcp"
    }
  }
}
```

Or use the CLI:

```bash theme={null}
claude mcp add --transport http noclick https://api.noclick.io/mcp
```

<Tip>
  Project-scoped config (`.mcp.json`) is recommended so your team can share the same setup via version control. You can also add it globally to `~/.claude.json` if you prefer.
</Tip>

### Authenticate

On first use, Claude Code will open your browser to authorize with your NoClick account. The token is saved automatically for future sessions.

<Warning>
  Keep the Claude Code session running while you approve in the browser — it hosts a temporary local server that receives the authorization. Closing the terminal (or approving from an old tab) breaks the hand-off with a "localhost refused to connect" error; just re-run `/mcp` → **Authenticate** and approve promptly.
</Warning>

### Verify

Ask Claude Code to list your workflows:

```
> List my NoClick workflows
```

***

## Cursor

Add to `.cursor/mcp.json` in your project root (or globally at `~/.cursor/mcp.json`):

```json theme={null}
{
  "mcpServers": {
    "noclick": {
      "url": "https://api.noclick.io/mcp"
    }
  }
}
```

Restart Cursor after saving. On first tool use, a browser window will open for OAuth authentication.

***

## Windsurf

Add to your Windsurf MCP config:

* **macOS/Linux**: `~/.codeium/windsurf/mcp_config.json`
* **Windows**: `%USERPROFILE%\.codeium\windsurf\mcp_config.json`

```json theme={null}
{
  "mcpServers": {
    "noclick": {
      "serverUrl": "https://api.noclick.io/mcp"
    }
  }
}
```

<Warning>
  Windsurf uses `serverUrl` (not `url`) for remote servers, which differs from other clients.
</Warning>

Restart Windsurf after saving.

***

## OpenAI Codex CLI

Add to `~/.codex/config.toml` (or `.codex/config.toml` in your project):

```toml theme={null}
[mcp_servers.noclick]
url = "https://api.noclick.io/mcp"
```

Or use the CLI:

```bash theme={null}
codex mcp add noclick --url https://api.noclick.io/mcp
```

***

## Claude (Web)

<iframe width="100%" height="400" src="https://www.youtube.com/embed/lBVY96kEv2c" title="Connect NoClick MCP to Claude" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen style={{ borderRadius: '8px', marginBottom: '16px' }} />

In Claude, go to **Settings > Connectors**, choose **Add custom connector**, and paste the URL:

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

This works on claude.ai and the Claude desktop app on all plans. Claude will open a browser window for OAuth authentication on first use.

***

## ChatGPT

<iframe width="100%" height="400" src="https://www.youtube.com/embed/b__nr5zP9i0" title="Connect NoClick MCP to ChatGPT" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen style={{ borderRadius: '8px', marginBottom: '16px' }} />

Custom MCP connectors in ChatGPT require developer mode (Plus, Pro, Business, Enterprise, and Edu plans; on team plans an admin must allow it first).

1. Go to **Settings > Apps & Connectors** and toggle **Developer mode** on under **Advanced settings**.
2. Back in **Apps & Connectors**, click **Create**.
3. Enter a name and paste the URL as the MCP Server URL:

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

4. In a chat, enable the connector from the **+** / tools menu.

ChatGPT will prompt you to authorize with your NoClick account.

***

## Claude Desktop

The easiest path on Claude Desktop is the custom connector flow described under [Claude (Web)](#claude-web) above; it works in the desktop app too. If you prefer a config-file setup, Claude Desktop's config uses stdio-based servers, so connect to NoClick's remote server through the `mcp-remote` wrapper:

* **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
* **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`

```json theme={null}
{
  "mcpServers": {
    "noclick": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.noclick.io/mcp"]
    }
  }
}
```

Fully quit and restart Claude Desktop after editing the config.

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authentication fails or times out">
    * Make sure you have a NoClick account at [noclick.com](https://noclick.com)
    * Check that pop-ups aren't blocked in your browser
    * Try clearing your browser cookies for noclick.com and re-authenticating
  </Accordion>

  <Accordion title="localhost refused to connect after clicking Allow">
    Your browser is being handed back to the CLI's temporary local login server, and nothing is listening anymore. This happens when the terminal session that started the authentication was closed or timed out, or when you approved from a tab opened by an earlier attempt.

    * Keep the CLI session open for the whole flow — don't close or interrupt it
    * Re-run the authentication (in Claude Code: `/mcp` → select the server → **Authenticate**) and approve promptly in the tab it opens
    * Don't reuse a link from a previous attempt — each attempt uses a fresh localhost port
    * Running the CLI over SSH or in a container? `localhost` refers to that machine, not your browser's — forward the callback port (`ssh -L <port>:localhost:<port> …`) or open the callback URL from that machine
  </Accordion>

  <Accordion title="Can't reach the NoClick server">
    * Verify your internet connection
    * Check if `https://api.noclick.io` is accessible from your network
    * If using a corporate network, you may need to configure proxy settings
  </Accordion>

  <Accordion title="Tools not showing up">
    * Restart your AI assistant after adding the MCP configuration
    * Verify the JSON/TOML syntax in your config file is valid
    * In Claude Code, run `claude mcp list` to verify the server is registered
    * In Cursor, check **Settings > Features > MCP Servers** for connection status
  </Accordion>

  <Accordion title="Windsurf: server not connecting">
    * Make sure you're using `serverUrl` (not `url`) in the config
    * Windsurf has a limit of 100 total tools across all MCP servers
  </Accordion>
</AccordionGroup>

## Next Steps

* [See all available MCP tools](/mcp/available-tools)
* Want the reverse, serving YOUR workflow's tools to MCP clients? [Create your own MCP server](/mcp/hosted-servers)
* [Build your first workflow](/getting-started/quickstart)