Abency
Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.
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
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
ask_aep_agent is undocumented by name. Its role is inferred from its name and Adobe's product description, not from the wire.core_switch_org is the widest-reaching tool. It moves the conversation to a different Adobe organization and is available to the model.openid, profile and email are identity only.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.
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.
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.
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.
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.
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.
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.
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.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-17https://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-17MCP Access permission item; redirects to the Coworker home page on 2026-11-17) · retrieved 2026-08-19https://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/.well-known/oauth-protected-resource returns the same body) · retrieved 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-17https://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-17Connect 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.