Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Query your organisation's own AI-agent telemetry in natural language.
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 Origin MCP server lets Claude, ChatGPT or any MCP-compatible agent question your own organisation's AI-agent telemetry in plain English. Origin is an endpoint AI observability platform, so the data is prompts, sessions, models and token spend captured from company laptops. Two tools: learn the analytics graph, then run one structured query against it.
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.
analytics_describe_schema returns every entity, field, metric and join edge, so the model knows the whole queryable surface before its first query.limit and a truncated flag bound each payload, but Origin publishes no default or maximum row count for a query.openid, profile, email and offline_access say nothing about the analytics grant a user is approving.support.originhq.com/robots.txt disallows all user agents, so the documentation cited here is reachable but not indexed.Your own organisation's AI activity, not a customer or finance dataset. Origin is an endpoint AI observability platform that inventories what AI agents do on company laptops. The MCP server exposes the same analytics graph behind Origin's dashboard: endpoints, AI prompts, sessions, models called, token spend, and tool-call chains, attributed to users and processes.
No. Origin documents a structured query object instead: an entity, joins, filters, a select list, metrics, ordering, paging, a time range and an optional sample. The model composes fields into that shape rather than writing SQL text, and malformed queries come back as validation errors. That containment is real and materially narrows the surface of a broad read grant.
Yes, and in unusual detail. Origin states every tool call is recorded to its audit log with the calling user, the tool name, a hash and snapshot of the arguments, the row count, bytes scanned, elapsed time and outcome. Records are scoped per tenant and retained for 30 days. This is the strongest audit posture in this catalogue.
Yes. Origin documents MCP queries as running with your user identity, and states you can only see what your Origin role allows in the dashboard. The roles are Admin and Member; both can read all tenant telemetry, so the practical grant for either role is the whole tenant's AI activity. Role separation governs configuration, not read scope.
Two, and Origin's documentation agrees with Anthropic's directory snapshot exactly. The vendor names `analytics_describe_schema` and `analytics_query`, states the server exposes two tools, and describes it as read-only with no ability to modify endpoints, agents or alerts. That matching count is rarer in this catalogue than it should be.
A tenant cost budget. Origin states queries exceeding it are rejected with a suggestion to narrow the scope, and that every response carries a cost object reporting rows and bytes scanned plus elapsed time. Results also carry a truncated flag, the time range defaults to 30 days, and requests are capped at a 256 KiB body.
Because Origin names its production estate that way throughout. The agent installation guide lists two more production hosts under the same convention. For a reader the practical value is unambiguity: the listed endpoint states plainly which environment you are connecting to, rather than leaving you to infer it from a bare vendor domain.
Not necessarily. Origin publishes a free Personal tier for one seat with 14-day retention and, in its own words, capped queries. Paid Team and Team Pro tiers extend retention to 30 and 90 days and add a monthly query cap or credit pack. The MCP server is not listed as a plan-gated feature, so entitlement follows your data access.
.md suffix) · retrieved 2026-08-19support.originhq.com/robots.txt disallows all user agents; www.originhq.com/robots.txt allows all crawlers except a /lp/ path and names AI crawlers individually. Neither publishes Content-Signal axes. support.originhq.com/sitemap.xml returns HTTP 404 (all fetched 2026-08-19) · retrieved 2026-08-19initialize POST to https://mcp.prod.originhq.com/mcp returns HTTP 401 with www-authenticate: Bearer realm="origin-mcp", resource_metadata="https://mcp.prod.originhq.com/.well-known/oauth-protected-resource/mcp" · retrieved 2026-08-19https://auth-web.dashboard.originhq.com/ as the authorization server; path-insert returns a 77-byte JSON unauthenticated error with HTTP 401 · retrieved 2026-08-19not_found body at both root and path-append forms (fetched 2026-08-19) · retrieved 2026-08-19S256 only, scopes_supported: ["email", "offline_access", "openid", "profile"], Dynamic Client Registration endpoint present) · retrieved 2026-08-19Connect Origin once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.