Connect Claude, Gemini, Copilot, ChatGPT, or any other MCP client 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, your MCP client can help you:
Find and switch between your Heatseeker workspaces when you have access to more than one.
Query live experiments to see what's running, what's complete, and how each variant performed.
Pull ad performance data such as top-performing ads, CTR, cost-per-lead, and historical campaign metrics.
Explore audience research and personas from research and persona profiles already built in Heatseeker.
Compare against competitor activity to understand what competitors are running and how it maps to your space.
Your assistant calls the available Heatseeker tools behind the scenes. Heatseeker enforces workspace permissions on every request.
Who can use it
Access to the Heatseeker MCP server is granted per workspace. Your Heatseeker workspace must have MCP access enabled before it appears in your MCP client. 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 (TODO: demo URL). 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
Server name:
HeatseekerTransport: Streamable HTTP
Auth: OAuth 2.0, handled by your MCP client
General MCP client setup
In your MCP client, add a new remote or custom MCP server.
Use the connection details above.
Complete the OAuth sign-in flow with your Heatseeker account.
Ask a Heatseeker question or run a Heatseeker tool to confirm the connection.
Exact menu names vary by client. Use the setup path for remote MCP servers, custom connectors, or Streamable HTTP servers in your client.
Example: Claude clients
Claude.ai and Claude Desktop use the same basic flow:
Open Settings, then Connectors.
Find Heatseeker in the connector directory or add it with the server URL.
Sign in with your Heatseeker account when the OAuth window opens.
For Claude Code, you can add the server with:
claude mcp add --transport https heatseeker <https://mcp.heatseeker.ai/mcp/heatseeker>
Run any Heatseeker tool to trigger the OAuth sign-in flow.
Available tools
Heatseeker MCP includes tools for finding workspaces, reviewing experiment and campaign performance, exploring personas, and asking broader marketing questions grounded in your Heatseeker data.
searchWorkspaces: Find Heatseeker workspaces you can access.getAllExperiments: Review completed or published experiments and variant performance.getTopAds: Find top or bottom imported campaign ads by performance metric.searchCampaignHistory: Search imported campaign history and creative performance.callDataAnalyst: Combine experiment, campaign, research, and persona evidence into an analytical answer.callHeatseekerAIAgent: Ask broader marketing questions using workspace context.listPersonas: See personas available in a workspace.chatWithPersonaAgent: Ask questions to a specific persona.
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.
Your connected client 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, 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 your MCP client.
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 your assistant to find and switch workspaces.
Support
Get help, request access, or report an issue: [email protected]