Adobe CX Enterprise Coworker

Connect Adobe CX Enterprise Coworker to Claude and other AI assistants.

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

What the Adobe CX Enterprise Coworker connector does

The Adobe CX Enterprise Coworker MCP server lets an AI client ask marketing questions of Adobe's agents after choosing an Adobe organization, Experience Platform sandbox and Customer Journey Analytics data view. Anthropic lists nine tools: eight set or list that context, and one, ask_aep_agent, passes the question on. Adobe says the answers are read-only.

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.

Adobe CX Enterprise Coworker tools (9)

  • ask_aep_agent
  • core_set_sandbox
  • core_set_dataview
  • core_set_sub_org
  • core_switch_org
  • core_list_sandboxes
  • core_list_dataviews
  • core_list_orgs
  • core_list_sub_orgs

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • We could not see any tool's schema. The endpoint returns 401 to an anonymous handshake, so the nine names come from Anthropic's directory. No descriptions, parameters or safety annotations were readable, and no tool here is annotated read-only as far as we can show.
  • ask_aep_agent is undocumented by name. Its role is inferred from its name and Adobe's product description, not from the wire.
  • Nothing listed clearly reads back the active context. The list tools show what you can reach, not what is currently set.
  • core_switch_org is the widest-reaching tool. It moves the conversation to a different Adobe organization and is available to the model.
  • The tool list changed completely between August and November 2026. None of the eight August names survives by exact name. Expect your client's list to differ from any snapshot, including this one.
  • The Firefly Image Generation skill is not available through Claude. Adobe lists it as a known limitation of Coworker in Claude.
  • Adobe does not support custom agent harnesses. Its guide says Coworker connects only to the AI platforms it lists; other MCP setups need a request through your Adobe representative.
  • The directory's documentation link is not publicly readable. It resolves to the Acrobat viewer shell with no document content.
  • The scopes grant no granularity. openid, profile and email are identity only.
  • Usage consumes AI credits from your Coworker allocation.
  • No published rate limits for this connector, so an agent discovers any throttle by hitting it.

Frequently asked questions

Which endpoint does the Adobe CX Enterprise Coworker MCP server use?

https://mcp.coworker.experience.adobe.io. Anthropic's 2026-11-17 directory snapshot lists it, and Adobe's current Coworker documentation gives the same URL for MCP clients. Two older hosts still answer with HTTP 401: the one this connector listed in August 2026 and the CX Coworker Gateway endpoint from Adobe's older install guide, which Adobe has since hidden from its navigation.

Does the Adobe CX Enterprise Coworker MCP server have a tool that returns marketing data?

One listed tool appears to, but we could not inspect it. The 2026-11-17 directory snapshot lists ask_aep_agent next to eight context tools, and its name points to a question routed to Adobe's agents. The endpoint refused an anonymous handshake, so we saw no schema or description for it. In August 2026 the listing had no such tool.

Can the Adobe CX Enterprise Coworker MCP server switch my sandbox or organization without me noticing?

It can switch them, and the current listing now includes tools to check. Five of the nine listed tools change the organization, sub-organization, sandbox or data view. Three list tools for organizations, sandboxes and data views now appear too, so you can ask the agent which ones you can reach. No listed tool clearly reports which context is active.

Is the Adobe CX Enterprise Coworker MCP server's OAuth descriptor standards-compliant?

Yes, on the current host. Its RFC 9728 descriptor returns a resource string, an authorization server on the same host and three scopes: openid, profile and email. The host this connector listed in August 2026 still serves a malformed descriptor, with a resources array and no authorization server or scopes, but the directory no longer points to it.

What Adobe entitlements do I need for the Adobe CX Enterprise Coworker MCP server?

A Coworker licence first, then product access. Adobe requires CX Enterprise Coworker to be provisioned for your organization, plus Experience Platform and at least one of Real-Time CDP, Journey Optimizer or Customer Journey Analytics. In Claude, an administrator must also approve the connector. Coworker inherits your existing Adobe permissions rather than adding a new permission model.

What does the Read + Write permission label on the Adobe CX Enterprise Coworker connector cover?

Mostly session context, on the evidence available. Five listed tools set or switch organization, sub-organization, sandbox or data view. Adobe states Coworker in AI platforms returns read-only insights and does not modify your customer data. We could not read the schema of ask_aep_agent, so whether it can start any other kind of write is unverified.

Does using the Adobe CX Enterprise Coworker connector consume Adobe AI credits?

Yes. Adobe states there is no extra charge for using Coworker in AI platforms, but usage draws from the same AI credits as other Coworker features. Its credit guide, read in August 2026, estimated 25 credits for a simple agent job and 50 for a more complex one, and warned that actual consumption varies.

Sources

  • Anthropic connector directory — https://claude.ai/directory/39d085c5-0b24-4a3f-aca1-5ec9d1726714 (snapshot 2026-11-17; source of the name Adobe CX Enterprise Coworker, the nine tool names, the endpoint, the Read + Write permissions label, the partner tier, the empty prompt list, the client list and the Claude Code install command). The 2026-08-16 snapshot is the source of the earlier name, endpoint and eight tool names · retrieved 2026-11-17
  • Adobe, Adobe CX Enterprise Coworker for AI Platforms — https://experienceleague.adobe.com/en/docs/coworker/content/ai-platforms (fetched 2026-11-17, HTTP 200; source file read from the AdobeDocs/coworker.en repository the same day; source of the endpoint for MCP clients, prerequisites, the Claude admin-approval step, the read-only and inherited-permissions statements, example prompts, known limitations, troubleshooting and the AI-credit statement) · retrieved 2026-11-17
  • Adobe, Session context tools in Adobe CX Coworker Gateway — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/mcp/mcp-get-started/context-tools (fetched 2026-11-17 as Markdown via the .md suffix, page last updated 2026-09-18; source of the six documented context tools and their hyphenated names, and the "set context once per session" guidance) · retrieved 2026-11-17
  • Adobe, Install Adobe CX Coworker Gateway — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/mcp/mcp-get-started/install (redirects to the Coworker home page on 2026-11-17; source file in the AdobeDocs/cx-enterprise-ai.en repository still names https://cx-coworker-gateway.adobe.io/mcp, and its commit history records the MCP docs being hidden from navigation and search on 2026-09-17) · retrieved 2026-11-17
  • Adobe, Access CX Coworker Gateway tools — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/mcp/mcp-get-started/access (read 2026-08-19; source of the MCP Access permission item; redirects to the Coworker home page on 2026-11-17) · retrieved 2026-08-19
  • Adobe, AI credits consumption — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/overview/ai-credit-consumption (read 2026-08-19; source of the 25-to-50 credit per-job estimates and the variability warning) · retrieved 2026-08-19
  • Live anonymous probe of https://mcp.coworker.experience.adobe.io — 2026-11-17: an initialize POST returned HTTP 401 with a www-authenticate Bearer challenge naming resource_metadata. No credentials were supplied and no tool was invoked · retrieved 2026-11-17
  • Live RFC 9728 descriptor — https://mcp.coworker.experience.adobe.io/.well-known/oauth-protected-resource/mcp/server/cx_coworker (fetched 2026-11-17; the root /.well-known/oauth-protected-resource returns the same body) · retrieved 2026-11-17
  • Live RFC 8414 metadata — https://mcp.coworker.experience.adobe.io/.well-known/oauth-authorization-server (fetched 2026-11-17; /.well-known/openid-configuration returns the same body; the path-insert form for /mcp/server/cx_coworker returns 404) · retrieved 2026-11-17
  • Former endpoints — https://aep-ai-ama.adobe.io/mcp and https://cx-coworker-gateway.adobe.io/mcp both returned HTTP 401 to an anonymous initialize on 2026-11-17. The former's descriptor at https://aep-ai-ama.adobe.io/.well-known/oauth-protected-resource returned a resources array on 2026-08-19 and again on 2026-11-17 · retrieved 2026-11-17
  • Directory documentation link — https://acrobat.adobe.com/id/urn%3Aaaid%3Asc%3AAP%3Adf8ae8a4-4404-4e39-9864-38a9bbbd0e68 (fetched 2026-11-17 with a browser user agent; HTTP 200, Acrobat viewer HTML titled "Adobe Acrobat", no document content readable) · retrieved 2026-11-17
  • Adobe support for this connector — https://helpx.adobe.com/enterprise.html (per the directory snapshot, 2026-11-17) · retrieved 2026-11-17
Use it in an agent

Put Adobe CX Enterprise Coworker to work.

Connect Adobe CX Enterprise Coworker once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.