Connect Claude to your Heatseeker workspace. Ask Claude about your live ad experiments, performance data, audiences, personas, and competitor activity in plain language — and get answers grounded in your real Heatseeker data.
Don't have Heatseeker yet? Request a demo to see how teams use Heatseeker to test ad creative at scale.
What you can do with it
Once connected, Claude can:
Find and switch between your Heatseeker workspaces when you have access to more than one.
Query live experiments — what's running, what's done, and how each variant performed.
Pull ad performance data — top-performing ads, CTR, cost-per-lead, and historical campaign metrics.
Talk to your audience research and personas — surface insights from research and persona profiles you've already built in Heatseeker.
Compare against competitor activity — what ads competitors are running and how that maps to your space.
You drive the conversation; Claude calls the right tools behind the scenes.
Who can use it
Access to the Heatseeker MCP server is granted per workspace. Your Heatseeker workspace must have MCP access enabled before it shows up in Claude. There is no self-serve toggle in the product today — enabling it goes through our team.
Already a Heatseeker user? Email [email protected] and ask us to enable MCP for your workspace. We'll confirm by reply.
Not a customer yet? Request a demo — we'll walk you through Heatseeker and the MCP integration together.
Setup
The Heatseeker MCP server is hosted by us — there's no software to install and no API key to manage. You sign in with the same Heatseeker account you use in the web app.
Connection details
Field | Value |
Server name |
|
Transport | Streamable HTTP |
URL | |
Auth | OAuth 2.0 (handled by your MCP client) |
Claude.ai (web) and Claude Desktop
Both use the same flow:
Open Settings → Connectors.
Find Heatseeker in the connector directory and click Add.
Sign in with your Heatseeker account when the OAuth window opens.
Claude Code (CLI)
Install with one command:
claude mcp add --transport https heatseeker <https://mcp.heatseeker.ai/mcp/heatseeker>
Run any Heatseeker tool to trigger the OAuth sign-in flow.
Note on other clients. The Heatseeker MCP server is currently supported only on Claude.ai (web), Claude Desktop, and Claude Code. Other MCP clients (Cursor, custom integrations) are not supported yet.
Authentication & permissions
The MCP server uses OAuth 2.0 with PKCE. Your client handles the flow — you just sign in with your Heatseeker account in the browser.
Claude only sees the same data you can see in the Heatseeker web app. Workspace boundaries and per-user permissions are enforced at the server.
There are no API keys to rotate or paste. To revoke access, sign out of Heatseeker or remove the connector from your MCP client.
Troubleshooting
You see an "access denied" page after signing in.
Your workspace does not have MCP access enabled yet. Email [email protected] and we'll turn it on.
Heatseeker tools don't appear in Claude.
Restart your MCP client. Double-check the server URL is exactly https://mcp.heatseeker.ai/mcp/heatseeker. If you opened the OAuth window but closed it before completing sign-in, trigger any Heatseeker tool to re-launch the flow.
Wrong workspace data is showing up.
You may be signed into a different Heatseeker account than expected. Sign out and sign back in with the right account, or ask Claude to switch workspaces.
Support
Get help, request access, or report an issue: [email protected]