Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Ask in plain English how visitors behave on your site: funnels, journeys, page metrics, errors.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Contentsquare MCP server lets Claude, ChatGPT or any MCP-compatible agent ask about how visitors behave on a website in plain English. It returns funnels, navigation journeys, page metrics, comparisons and error rankings — all aggregate. Sign-in is OAuth 2.1 under one scope named metrics, and every analytics call draws down a published per-plan allowance.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
resource_documentation is broken. The OAuth descriptor points at https://api.contentsquare.com/docs, which returned 404 on 2026-08-19.client_credentials is advertised but undocumented for MCP. A machine-to-machine token has no user whose project permissions it could inherit.No tool in the listed set reaches replay or individual-session data. All 21 tools are aggregate-shaped: metrics, funnels, journeys, page comparisons and error rankings. Contentsquare's own MCP article names five analysis capabilities, none of them Session Replay, and describes the underlying Metrics API as exporting aggregated data. The in-app product does expose replays; the connector does not.
Contentsquare classifies it as a configuration tool rather than an analytics one, alongside the search and recommend tools, so it does not count against your tool-call allowance. Its name and that classification point to a feedback channel about the MCP server itself, not a write into Contentsquare data. Contentsquare publishes no argument schema or description for it, so the exact payload is unverified.
Yes. Contentsquare states you can only access projects where you already have permissions in Contentsquare, and lists project access as a prerequisite before setup. The connector therefore inherits the connecting user's project scope rather than reaching every project on the account. Setup itself is restricted further: Contentsquare states only Admins can set up and use the integration.
Yes, it is metered. Contentsquare publishes a tool-call allowance per plan: up to 300 per month on Free, 36k per year on Growth, 72k on Pro and 108k on Enterprise. Allowances are tracked at account level and shared by every connected user. Only analytics tools count; configuration tools do not. Hitting the limit stops the server processing new requests.
Anthropic's directory snapshot lists 21, and Contentsquare's own documentation corroborates that number rather than contradicting it. The support article names ten configuration tools explicitly and describes five analysis capabilities covering the other eleven. Contentsquare publishes no per-tool reference with argument schemas, so the names are confirmed but their inputs and outputs are not documented.
No. Contentsquare states the integration is available on Free, Growth, Pro and Enterprise plans, and the Free plan is self-serve. Two gates still apply. Only Admins can set up the integration, and the five error tools depend on Error Analysis, which Contentsquare sells as Experience Monitoring — included with Enterprise, an add-on to Pro.
A single scope named metrics. We verified it live on 2026-08-19: the protected-resource descriptor and the authorization-server metadata both declare it, and neither advertises any other. The name is unusually well matched to the surface, since every tool computes or retrieves aggregate metrics. One scope cannot separate reading from writing, but here there is little writing to separate.
/api/v2/help_center/en-us/articles/41563169756945.json; article last updated 2026-07-07). The only dedicated MCP article — a help-centre search for "Model Context Protocol" returned no second one · retrieved 2026-08-19contentsquare.com/robots.txt allows all listed AI crawlers, including ClaudeBot, GPTBot and anthropic-ai, and publishes no Content-Signal axes; support.contentsquare.com/robots.txt is a stock Zendesk file with no Content-Signal axes and no MCP-relevant disallows. support.contentsquare.com/llms.txt returns 404 · retrieved 2026-08-19initialize POST to https://api.contentsquare.com/mcp returns HTTP 401 with www-authenticate: Bearer resource_metadata="https://api.contentsquare.com/.well-known/oauth-protected-resource/mcp". No tool call was made and no authentication was attempted · retrieved 2026-08-19scopes_supported: ["metrics"]; root and path-insert both return 68-byte JSON 404 errors · retrieved 2026-08-19S256 only, scopes_supported: ["metrics"], client_secret_post and client_secret_basic client authentication) · retrieved 2026-08-19resource_documentation target — https://api.contentsquare.com/docs returned HTTP 404 on 2026-08-19 · retrieved 2026-08-19permissions: "Read", no prompts listed) · retrieved 2026-08-16Connect Contentsquare once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.