Skip to main content
Both LanderLab and ClickFlare run their own MCP servers. Once you connect both to the same AI assistant, you can add a landing page to ClickFlare by asking for it in plain English, instead of copying URLs between two dashboards. This guide uses Claude, but the same steps work in any MCP client.

​
What You Need

  • A LanderLab account with at least one landing page.
  • A ClickFlare account.
  • Claude on the web or Claude Desktop.

​
Setup

1

Connect LanderLab to Claude

  1. Open Claude and go to Settings > Connectors.
  2. Click Browse connectors, search for LanderLab, and select it.
  3. Click Connect, sign in to LanderLab, and click Authorize.
  4. Review the tool permissions. Set the tools you use often to Always allow so Claude does not ask on every action.
LanderLab is a listed connector, so there is no URL to paste. Full walkthrough: Connect LanderLab to Claude.ai via MCP.
2

Create a ClickFlare API key

  1. Log in to ClickFlare and open Settings > API Keys.
  2. Click Create API key, give it a descriptive name, and click Generate.
  3. In the Your API Key window, switch from the HTTP tab to the MCP tab.
  4. Copy the MCP server URL. It already contains your API key. 'api Clickflare 1
The key is shown only once. Copy it before you close the window, and store it somewhere safe. Anyone who has the MCP server URL can reach your ClickFlare account, so treat it like a password.
3

Add ClickFlare as a custom connector

ClickFlare is not in Claude’s connector directory yet, so you add it manually.
  1. Go back to Settings > Connectors in Claude and click Add > Add custom connector.
  2. Set Name to ClickFlare.
  3. Paste the MCP server URL from the previous step into Remote MCP server URL, then click Continue. Image
  4. Leave Authentication set to None. The API key is already inside the URL, so no OAuth sign-in and no request headers are needed.
  5. Click Add, then click Connect on the ClickFlare connector.
4

Send the lander to ClickFlare

Start a new chat and ask for it directly. You can point at the lander by URL or by name:
Claude pulls the page URL from LanderLab, then creates the lander in ClickFlare. Approve the tool calls when prompted.
If Claude asks how many CTAs the page has, answer with the number of offer links on the page. ClickFlare uses it to build the click URLs.

​
Verify It Worked

Open ClickFlare and go to Assets > Landers. The new lander appears in the list with the name and URL you gave it, ready to drop into a campaign or flow.

​
Example Prompts

  • “List my LanderLab landers and tell me which ones are not in ClickFlare yet”
  • “Add my three published landers to ClickFlare with the same names”
  • “Create a ClickFlare lander from the Summer Offer preview URL, 2 CTAs”
  • “Rename the Summer Offer lander in ClickFlare to Summer Offer V2”

​
Troubleshooting

ClickFlare tools do not show up. Reopen the connector and confirm it shows as connected. Then start a new chat, since tools load at the start of a conversation. 401 or invalid API key. The key was revoked or the URL was copied incomplete. Create a new API key in ClickFlare, copy the full MCP server URL, and update the connector. Claude asks for the lander URL. The page has no URL yet. Publish the lander, or give Claude the preview URL instead. The lander lands in the wrong workspace. Name the workspace in your prompt, for example “add it to ClickFlare in the Media Buying workspace”.