ClickFunnels

You run a ClickFunnels MCP Server that connects Claude Desktop to your ClickFunnels data. This server exposes endpoints to list funnels and contacts and to fetch individual funnels, enabling you to interact with ClickFunnels workflows directly from your MCP client.

How to use

Start the MCP server so Claude Desktop can communicate with ClickFunnels. You will run the server as a local process and connect Claude Desktop to it via the provided SSE endpoint. Once running, you can use your MCP client to list funnels, view a specific funnel by ID, or list contacts from your ClickFunnels account. The server handles authentication and API requests using the configured environment variables.

To use the server from Claude Desktop, ensure the client is configured to connect to the local SSE stream at http://localhost:3002/sse and that the server process is running in the background or foreground. You can adjust logging to debug level to diagnose issues during setup.

How to install

Prerequisites you need before installation: Node.js and npm installed on your system. Ensure you have a working environment where you can create and edit configuration files.

# 1) Clone the MCP server repository
git clone https://github.com/illGATESmusic/click-funnels-mcp-shared.git
cd click-funnels-mcp-shared

# 2) Install dependencies
npm install

# 3) Build the project
npm run build

Configure environment variables for the server and integrate it with Claude Desktop. Create or update your environment file and Claude Desktop configuration to point to the local server. Use the following environment variables as placeholders until you replace them with your real values.

PORT=3002
CLICKFUNNELS_API_BASE=https://your-domain.myclickfunnels.com/api/v2
CLICKFUNNELS_WORKSPACE_ID=123456
CLICKFUNNELS_API_TOKEN=YOUR_API_TOKEN_HERE
CLICKFUNNELS_WORKSPACE_SUBDOMAIN=your-subdomain
NODE_ENV=production
MCP_LOG_LEVEL=debug
MCP_LOG_TO_CONSOLE=true
MCP_LOG_TO_FILE=true
MCP_LOG_DIR=/absolute/path/to/click-funnels-mcp-shared/logs
NODE_OPTIONS=--max-old-space-size=256

Next, configure Claude Desktop to start the MCP server. Create or edit your Claude Desktop configuration to register the server and its runtime command. Use the absolute path to the built server and ensure the working directory points to the repository. The example below shows the required structure and variables.

{
  "mcpServers": {
    "clickfunnels_mcp": {
      "command": "node",
      "args": ["/absolute/path/to/click-funnels-mcp-shared/dist/index.js"],
      "env": {
        "PORT": "3002",
        "CLICKFUNNELS_API_BASE": "https://your-domain.myclickfunnels.com/api/v2",
        "CLICKFUNNELS_WORKSPACE_ID": "123456",
        "CLICKFUNNELS_API_TOKEN": "YOUR_API_TOKEN_HERE",
        "CLICKFUNNELS_WORKSPACE_SUBDOMAIN": "your-subdomain",
        "NODE_ENV": "production",
        "MCP_LOG_LEVEL": "debug",
        "MCP_LOG_TO_CONSOLE": "true",
        "MCP_LOG_TO_FILE": "true",
        "MCP_LOG_DIR": "/absolute/path/to/click-funnels-mcp-shared/logs",
        "NODE_OPTIONS": "--max-old-space-size=256"
      },
      "cwd": "/absolute/path/to/click-funnels-mcp-shared"
    }
  },
  "mcpServerConnections": [
    {
      "url": "http://localhost:3002/sse"
    }
  ]
}

Additional notes

Troubleshooting tips help you diagnose common setup issues. Review the logs at the path you configure for MCP logs to identify authentication problems, incorrect workspace IDs, or network/API errors. If a problem remains unresolved, confirm that the server process is running and that Claude Desktop is set to connect to the correct SSE endpoint.

Security best practices include keeping API tokens secret, using a dedicated workspace for integration, and restricting network access to the local machine where Claude Desktop runs. Rotate API credentials if you suspect they have been compromised.

Troubleshooting tips

If you encounter issues, check the logs for detailed errors. Common problems include missing directories, incorrect paths, or environment variables not being picked up by the runtime. Ensure the working directory in Claude Desktop matches the location of the MCP server and that the build output exists at the expected path.

Security and maintenance

Keep dependencies up to date by periodically running installation and build steps. Store API credentials securely and avoid embedding them in code repositories. Use production-ready settings for NODE_ENV and log levels in your deployment environment.

Available tools

debug

Provides debugging information about the current environment

list_funnels

Lists all funnels from your ClickFunnels account

get_funnel

Gets a specific funnel by ID

list_contacts

Lists contacts from your ClickFunnels account