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
Claude Code
The recommended way to connect. Add NoClick to your project’s
.mcp.json file in the project root:
Authenticate
On first use, Claude Code will open your browser to authorize with your NoClick account. The token is saved automatically for future sessions.Verify
Ask Claude Code to list your workflows:Cursor
Add to.cursor/mcp.json in your project root (or globally at ~/.cursor/mcp.json):
Windsurf
Add to your Windsurf MCP config:- macOS/Linux:
~/.codeium/windsurf/mcp_config.json - Windows:
%USERPROFILE%\.codeium\windsurf\mcp_config.json
OpenAI Codex CLI
Add to~/.codex/config.toml (or .codex/config.toml in your project):
Claude (Web)
In Claude, go to Settings > Connectors, choose Add custom connector, and paste the URL:
ChatGPT
Custom MCP connectors in ChatGPT require developer mode (Plus, Pro, Business, Enterprise, and Edu plans; on team plans an admin must allow it first).
- Go to Settings > Apps & Connectors and toggle Developer mode on under Advanced settings.
- Back in Apps & Connectors, click Create.
- Enter a name and paste the URL as the MCP Server URL:
- In a chat, enable the connector from the + / tools menu.
Claude Desktop
The easiest path on Claude Desktop is the custom connector flow described under 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 themcp-remote wrapper:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Troubleshooting
Authentication fails or times out
Authentication fails or times out
- Make sure you have a NoClick account at noclick.com
- Check that pop-ups aren’t blocked in your browser
- Try clearing your browser cookies for noclick.com and re-authenticating
localhost refused to connect after clicking Allow
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?
localhostrefers to that machine, not your browser’s — forward the callback port (ssh -L <port>:localhost:<port> …) or open the callback URL from that machine
Can't reach the NoClick server
Can't reach the NoClick server
- Verify your internet connection
- Check if
https://api.noclick.iois accessible from your network - If using a corporate network, you may need to configure proxy settings
Tools not showing up
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 listto verify the server is registered - In Cursor, check Settings > Features > MCP Servers for connection status
Windsurf: server not connecting
Windsurf: server not connecting
- Make sure you’re using
serverUrl(noturl) in the config - Windsurf has a limit of 100 total tools across all MCP servers
Next Steps
- See all available MCP tools
- Want the reverse, serving YOUR workflow’s tools to MCP clients? Create your own MCP server
- Build your first workflow