Contentsquare MCP Server

Contentsquare's MCP (Model Context Protocol) server is an official, provider-hosted integration that acts as a secure bridge between AI agents and your Contentsquare experience analytics data. Instead of logging into the Contentsquare dashboard, users query behavioral data, conversion funnels, page metrics, journeys, and segments in natural language directly from their preferred AI client.

The server is hosted by Contentsquare and authenticates via OAuth2, with access tokens that expire hourly and refresh automatically through the connected agent. Users only see projects they already have permissions for in Contentsquare, so existing role-based access controls carry over. Setup is performed inside the Contentsquare platform under "Analysis setup > Model Context Protocol (MCP)", where you select your AI agent and follow a guided flow rather than copying a manual server URL.

Contentsquare ships integrations for Claude (Desktop and Code), Cursor, VS Code, Dust, ChatGPT, and Microsoft Copilot, plus any other MCP-compatible agent. Each Contentsquare plan includes a tool call allowance specific to the MCP integration, and only analytics data tool calls count against the quota (configuration-retrieval calls like listing projects do not).

Tools

Prerequisites

• A Contentsquare account with access to at least one project.
• An MCP-compatible AI client: Claude Desktop, Claude Code, Cursor, VS Code, Dust, ChatGPT, or Microsoft Copilot.
• Your Contentsquare plan must include an MCP tool call allowance (contact your CSM if unsure).

Setup steps

1. Sign in to Contentsquare and open the main menu.
2. Click Analysis setup, then Model Context Protocol (MCP).
3. Select your target AI agent (Claude, Cursor, VS Code, Dust, ChatGPT, Copilot, etc.).
4. Follow the in-app instructions to copy the generated server endpoint and complete the OAuth handshake from your AI client.
5. Approve the OAuth scopes when prompted. Tokens are valid for 1 hour and refresh automatically.

Example client config

The exact URL is generated per tenant inside the Contentsquare UI. For a Claude Desktop / Cursor style config, the generated entry typically looks like:

{
  "mcpServers": {
    "contentsquare": {
      "url": "<URL_PROVIDED_BY_CONTENTSQUARE_SETUP>",
      "transport": "http"
    }
  }
}

For Claude Code, you can add the connector from the CLI once you have the URL from the setup screen:

claude mcp add contentsquare --transport http "<URL_PROVIDED_BY_CONTENTSQUARE_SETUP>"

Notes

• All data transfer is secured with OAuth2. Contentsquare credentials are never passed directly to the AI agent.
• You can only query projects you already have permission to access in Contentsquare.
• If the agent stops returning data, re-authenticate through your client's connector settings.

• Ask an AI agent "Where are users dropping off in our checkout funnel this week, and which device types are most affected?" without opening the Contentsquare dashboard.
• Detect JavaScript errors or API failures over the last 24 hours and correlate them with affected segments and conversion impact.
• Build journey maps by asking which pages users most often visit before completing signup, and which pages correlate with exits.
• Compare conversion rates across device types, traffic sources, and regions to surface segment-level performance gaps.
• Benchmark campaign landing pages, pulling engagement and conversion metrics for each variant to identify winning design patterns.

• "List my Contentsquare projects and show the top 5 pages by bounce rate in the EU project for the last 7 days."
• "Compare mobile vs desktop conversion rate on the checkout funnel for the last 30 days."
• "Which pages are causing the highest frustration signals on our app this week?"
• "Create an export job for all sessions where users hit the pricing page but did not convert in the last 14 days."
• "Pull engagement metrics for our Black Friday landing pages and tell me which one has the strongest scroll depth."

• Official, provider-hosted server maintained by Contentsquare, with no self-hosting required.
• OAuth2 with automatic token refresh and inherited role-based access controls, so users only see what they are already entitled to.
• Broad client support out of the box: Claude Desktop, Claude Code, Cursor, VS Code, Dust, ChatGPT, and Copilot.
• Covers configuration discovery (projects, segments, mappings, zonings) and analytics retrieval (site and page metrics, exports) in a single connector.

• Requires a Contentsquare subscription with an MCP tool call allowance, and analytics calls count against quota.
• The server URL is generated per tenant inside the Contentsquare UI, so there is no public endpoint or open-source repo to inspect.
• Public documentation of the exact tool surface is limited; some tool names and parameters must be discovered at runtime by the agent.

• Amplitude MCP server for product analytics and behavioral queries.
• Mixpanel MCP integrations for event analytics and funnel analysis.
• Google Analytics 4 MCP server for traffic, conversion, and audience reporting.