Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Triage data-quality alerts, trace lineage, read query history and create monitors.
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 Monte Carlo MCP server connects your data observability account to Claude, ChatGPT, Cursor and any MCP-compatible agent. It exposes 25 tools for triaging data-quality alerts, tracing lineage, reading query history and creating monitors. Sign-in is OAuth, and the connector writes as well as reads — it can restage an alert someone else is working.
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.
delete, remove, archive, mute or silence verb appears in the 25 listed names, the 14 named in Monte Carlo's docs, or the 67 in its Agent Toolkit.mcp/access is required to connect at all. Writes additionally need mcp/edit, which the Viewer role lacks. Monte Carlo's MCP page states Editor or above is required, contradicting its own IAM table.extended and agent_observability tools are unavailable unless the client sends the x-mcd-toolset header.mcp.getmontecarlo.com. The root resource descriptor names a regional host, mcp.us1.getmontecarlo.com, indicating regional deployments of the same SaaS. Monte Carlo documents no self-hosted MCP Server.Monte Carlo's reference page names two causes. Verify the endpoint URL, because the key-based mcp-remote setup expects a trailing slash rather than the bare path used by OAuth clients. Then confirm npx is on your PATH, since the bridge auto-installs only when the -y flag can reach npm.
Check the credential itself before the client. Monte Carlo tells you to re-check the Key id and Key secret, confirm the headers are passed in one of the two supported forms, and verify the key type is MCP server. Standard Monte Carlo API keys will not work with the MCP Server at all.
Usually an outdated MCP client rather than a permissions problem. Monte Carlo's advice is to upgrade to the latest version. If your console shows an empty Authorization header, the token is not being passed, which the vendor attributes to older client versions that silently omit custom headers.
Viewer. Monte Carlo's built-in roles reference grants Viewer the mcp/access permission for read-only MCP tools, and it is the only one of the six built-in roles with no MCP Edit row. Responder adds write access while staying read-only elsewhere, which suits alert triage.
It can set the status, which is how Monte Carlo records resolution. Statuses run from Acknowledged through Work in progress, Fixed, Expected and No action needed. Monte Carlo states plainly that alert statuses do not feed back into the models generating thresholds, so a status change never retunes detection.
Yes. getQueriesForTable returns query history, which Monte Carlo's toolkit documents as read and write queries against a table. The Performance documentation shows query text attributed to users and tools such as Looker, retained for the most recent four weeks, so business logic and literal values can appear.
Yes, by IP address. Monte Carlo publishes a dedicated MCP scope in its Network Access Control Lists covering the mcp.getmontecarlo.com/mcp endpoint. Only requests from allowlisted addresses are permitted once configured, managed in Settings under Network access controls or through the GraphQL API.
Connect Monte Carlo once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.