Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Ask your governed Omni model a question, get warehouse data back.
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 Omni Analytics MCP server lets Claude, ChatGPT or any MCP-compatible agent question a company's governed BI model in plain English. The agent picks an Omni model, narrows to a curated topic, and runs a query that executes against your own data warehouse. Sign-in is OAuth 2.1, and Omni documents every MCP query as running with the authenticated user's permissions.
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.
getData requires Single shot query generation, which Omni states is disabled by default. A default organisation does not serve it.403 Feature is not enabled.pickTopic reads pickModel's choice and getData runs against both. Omni documents no behaviour for a wrong selection.askOmni can save model edits to a branch and create scheduled routines that deliver by email or Slack.listBranches ignores those headers.X-MCP-Query-All-Views lets the AI query any view in the model rather than only curated topics.compute_routing names MCP traffic under an agentic job type.runQuery defaults to 500 and caps at 10,000.Yes. Omni documents that every MCP query runs with the authenticated user's permissions, and that interactions are scoped to the model and topic supplied to the server. The modelling layer's controls apply underneath: access grants gate topics, views and individual fields, while access filters restrict rows by user attribute. An OAuth connection inherits your in-app permissions exactly.
Yes, in effect. Omni documents `pickTopic` as returning topics in the model selected by `pickModel`, and `getData` as executing against the selected model and topic. The selection carries forward rather than travelling as arguments you can inspect. You can remove the ambiguity by pinning a model and topic with connection headers, which skips the picking steps entirely.
Anthropic's directory snapshot lists three. Omni's own tool reference documents eight: the three listed plus `runQuery`, `askOmni`, `checkStatus`, `listBranches` and `searchOmniDocs`. Which ones actually appear depends on organisation settings — `getData` and `runQuery` need Single shot query generation, which Omni states is disabled by default, so the listed set is not the served set.
Yes, twice over. Omni states that MCP Server usage consumes AI credits alongside its other AI features, with cost rising for complex multi-step analysis and larger data models. Separately, each query executes against your own warehouse. Omni's `compute_routing` setting names MCP traffic explicitly under an `agentic` job type so admins can route it to a dedicated warehouse.
A model is Omni's semantic layer over a database connection — tables, joins, fields and business logic in a three-layer structure. A topic is a curated dataset inside a model: a base table plus its joins, measures and dimensions, shaped for one business use case. Omni describes topics as shielding end-users from raw schemas. Together they bound what the agent can query.
Usually yes. Omni requires an Organization Admin to enable Enable AI, Omni Agent, and the MCP server setting, plus each individual tool capability. The MCP server setting is on by default; Single shot query generation, which powers `getData`, is not. Disabling MCP returns a 403 to new authorizations and blocks existing grants from calling tools.
Because it is a shared OAuth entry point, not your instance. Omni states this URL routes requests to your Omni organization after you identify yourself during the OAuth flow, which is why one host works for every customer. API key connections skip it and point at your own instance path instead. Omni warns the flow follows your most recent login cookie.
.md suffix) · retrieved 2026-08-19compute_routing model parameter — https://docs.omni.co/modeling/models/compute-routing (fetched 2026-08-19) · retrieved 2026-08-19default_row_limit model parameter — https://docs.omni.co/modeling/models/default-row-limit (fetched 2026-08-19) · retrieved 2026-08-19docs.omni.co/robots.txt publishes Content-Signal: ai-train=yes, search=yes, ai-input=yes; omni.co/robots.txt allows all crawlers and publishes no Content-Signal axes · retrieved 2026-08-19initialize POST to https://callbacks.omniapp.co/callback/mcp returns HTTP 401 with www-authenticate: Bearer resource_metadata="https://callbacks.omniapp.co/.well-known/oauth-protected-resource", scope="mcp:access", error="invalid_token" · retrieved 2026-08-19mcp:access; path-insert returns a 237 KB HTML application shell with HTTP 200 · retrieved 2026-08-19S256 only, scopes_supported: ["mcp:access"]) · retrieved 2026-08-19Connect Omni Analytics once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.