Adobe Marketing Agent

Name: Adobe Marketing Agent MCP Server
Availability: InStock
Author: Adobe Marketing Agent

Sales & CRM8 tools

Set the Adobe organization, Experience Platform sandbox and Customer Journey Analytics data view an agent works inside. All eight listed tools are session context, preferences or feedback — none returns marketing data. The marketing answers come from Adobe agents invoked server-side, and Adobe's own MCP documentation points at a different endpoint.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Adobe Marketing Agent via MCP

https://aep-ai-ama.adobe.io/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Adobe Marketing Agent Tools & Capabilities (8)

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

Limits

No tool returns marketing data. All eight listed tools are session context, preferences or feedback. Anything an agent tells you about an audience, campaign or journey came from an Adobe agent invoked server-side, not from a tool you can name, inspect or audit.
Nothing listed reads the active context back. Adobe documents core-list_orgs, core-list_sandboxes and core-list_dataviews for its gateway, and none of the three is in this connector's listing. An agent can change org and sandbox; no listed tool reports what they are.
core-switch_org is the widest-reaching tool here. It relocates the conversation to a different Adobe organization — a different customer estate — and it is available to the model.
The Read + Write label overpromises. Every write on the listed surface is session state, a stored preference or feedback. Adobe states the Marketing Agent does not create or update marketing assets or configurations.
Adobe's documentation names a different endpoint. Its install guide directs MCP clients to https://cx-coworker-gateway.adobe.io/mcp; aep-ai-ama.adobe.io appears nowhere in Adobe's Experience League documentation. We did not establish the relationship between the two hosts.
The directory's documentation link is not publicly readable. It resolves to the Acrobat viewer shell with no document content. A share link can be revoked or replaced, offers no citable version history, and may become unreachable.
The RFC 9728 descriptor is malformed. It returns a resources array instead of a resource string and omits both authorization_servers and scopes_supported. A strict client following the specification may not discover the authorization server at all.
The scopes grant no granularity. openid, email and profile are identity only. Nothing at consent distinguishes reading from switching an org.
We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no schemas, parameters or safety annotations were readable. No tool here is annotated read-only as far as we can show — the table's classifications are inferred from names and Adobe's docs, not read from the wire.
Five of the eight listed tools appear in no Adobe documentation. Both widget tools, both feedback tools and core-user_preferences. We cannot say what a stored preference contains or how long it persists.
The tool list is entitlement-dependent. Adobe states only entitled tools are surfaced, so the eight names describe one snapshot, not a contract. Your client may report a different set.
Three of six product families are Beta or Preview. Real-Time CDP, Experience Platform and Journey Optimizer tools all require Beta enablement per Adobe's access table.
Organization enablement is not self-service. Adobe gates the whole surface at tenant level and routes requests through an account team, so an admin cannot unblock it alone.
Feedback leaves your tenant. core-provide_feedback sends text to Adobe, and feedback written about a marketing answer can carry more than intended.
Usage consumes AI credits. Adobe publishes estimates of 25 to 50 credits per agent job and warns that actual consumption varies with the steps executed.
No published rate limits for this connector, so an agent discovers any throttle by hitting it.

Frequently asked questions

Does the Adobe Marketing Agent MCP server have any tools that return marketing data?

No. All eight tools named in Anthropic's snapshot set session context, store preferences or send feedback. There is no query tool, no audience tool and no report tool in the listing. The marketing answers come from Adobe agents the server invokes behind the connector, which Adobe documents as being chosen by the prompt rather than called directly.

Can the Adobe Marketing Agent MCP server switch my sandbox or organization without me noticing?

Yes, and nothing in the listed tool set reads the context back. Three of the eight tools change organization, sandbox or data view, and Adobe documents no listed tool that reports which is active. Adobe documents three companion list tools that would answer the question, and none of them appears in the directory listing for this connector.

What does the Read + Write permission label on the Adobe Marketing Agent connector actually cover?

Session state and feedback, on the evidence available. Every write among the eight listed tools sets context, stores a preference or submits feedback. Adobe separately states the Marketing Agent returns read-only insights and does not create or update marketing assets or configurations, so the label promises far more reach than the listed surface delivers.

Which endpoint does Adobe document for connecting an MCP client to Adobe marketing data?

A different one. Adobe's MCP install guide names a single CX Coworker Gateway endpoint for all documented product tools, and the host in Anthropic's directory listing appears nowhere in Adobe's Experience League documentation. Both hosts answer live and both demand OAuth, so treat the listed connector as a separate surface rather than the documented one.

What Adobe entitlements do I need for the Adobe Marketing Agent MCP server?

Organization enablement first, then per-product permissions. Adobe requires an Adobe organization to be enabled before any of these tools work, and states that only tools your organization and credentials are entitled to use will appear. Customer Journey Analytics and Adobe Analytics additionally require an MCP Access permission item in an Adobe Admin Console product profile.

Is the Adobe Marketing Agent MCP server's OAuth descriptor standards-compliant?

No. Its RFC 9728 document returns a resources array rather than the resource string the specification defines, and omits both authorization_servers and scopes_supported. Scopes had to be read from the authorization-server metadata instead. Adobe's own gateway host publishes a correctly shaped descriptor at the same time, so this is one host's defect.

Does using the Adobe Marketing Agent consume Adobe AI credits?

Yes, through the agents it invokes rather than the connector itself. Adobe states the Marketing Agent calls different Adobe agents and jobs depending on the prompt, and that the invoked agent consumes AI credits. Its published estimates run from 25 credits for a simple agent job to 50 for a more complex one, and it warns actual consumption varies.

Sources

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-08-19 as Markdown via the .md suffix; source of the six documented core- tools, the three list tools absent from this listing, the sandbox-sharing behaviour, and the "set context once per session" guidance) · retrieved 2026-08-19
Adobe, Adobe CX Coworker Gateway overview — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/mcp/overview (fetched 2026-08-19; source of the gateway endpoint, the six product tool families with their availability, and the statement that only entitled tools are surfaced) · retrieved 2026-08-19
Adobe, Access CX Coworker Gateway tools — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/mcp/mcp-get-started/access (fetched 2026-08-19; source of the organization-enablement gate, the per-product access table, and the MCP Access permission item requirement) · retrieved 2026-08-19
Adobe, Install Adobe CX Coworker Gateway — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/mcp/mcp-get-started/install (fetched 2026-08-19; source of the documented endpoint, the statement that no keys or tokens belong in client configuration, and the product-context guidance) · retrieved 2026-08-19
Adobe, Adobe Marketing Agent for Microsoft 365 Copilot — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/agents/ama-ms (fetched 2026-08-19; source of the context setter and feedback UI descriptions, the statement that the agent invokes different Adobe agents and jobs by prompt, the read-only insight statements, and the underlying agent list). Note: this page documents the Microsoft 365 Copilot surface of the Marketing Agent, not the MCP connector; it is cited for the agent's behaviour and UI, which the two surfaces share · retrieved 2026-08-19
Adobe, Adobe Experience Platform Agent Orchestrator — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/agents/agent-orchestrator (fetched 2026-08-19; source of the statement that the gateway is the unified MCP endpoint for CX Enterprise, and of the sandbox and data view selection description) · retrieved 2026-08-19
Adobe, AI credits consumption — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/overview/ai-credit-consumption (fetched 2026-08-19; source of the 25-to-50 credit per-job estimates for the Audience, Data Insights and Journey agents, and the variability warning) · retrieved 2026-08-19
Adobe, Agentic AI Monitoring dashboard — https://experienceleague.adobe.com/en/docs/cx-enterprise-ai/experience-cloud-ai/overview/monitoring (fetched 2026-08-19; source of the production-sandbox-only monitoring limitation and Adobe's own warning about mistaking the selected sandbox) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor — https://aep-ai-ama.adobe.io/.well-known/oauth-protected-resource (fetched 2026-08-19; root form returns 200 with a 49-byte body carrying a resources array and no authorization_servers or scopes_supported; both path-insert and path-append forms return 404 with byte-identical bodies) · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — https://aep-ai-ama.adobe.io/.well-known/oauth-authorization-server (fetched 2026-08-19; source of the three scopes, the self-hosted issuer and endpoints, the grant and PKCE configuration; the OpenID configuration document at the same host returns an identical body). Compared against https://cx-coworker-gateway.adobe.io/.well-known/oauth-protected-resource (fetched 2026-08-19), which is correctly formed · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an anonymous POST to the endpoint returns HTTP 401 with a www-authenticate Bearer challenge naming resource_metadata; a plain GET returns HTTP 406 demanding an event-stream Accept header. No credentials were supplied and no tool was invoked · retrieved 2026-08-19
Directory documentation link — https://acrobat.adobe.com/id/urn:aaid:sc:AP:5799e952-be87-4829-b0c4-6f82ca8e8b8b (fetched 2026-08-19 with a browser user agent; returns HTTP 200 and roughly 740 KB of Acrobat viewer application HTML titled "Adobe Acrobat", with no document content readable) · retrieved 2026-08-19
experienceleague.adobe.com/robots.txt (fetched 2026-08-19) allows all crawlers, advertises the .md suffix for every documentation URL and links its own llms.txt, which is how each documentation URL above was located rather than guessed. No Content-Signal line is present on either that file or developer.adobe.com/robots.txt (fetched 2026-08-19), so no use-side restriction is expressed · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/39d085c5-0b24-4a3f-aca1-5ec9d1726714 (snapshot 2026-08-16; source of the eight tool names, the Read + Write permissions label, the partner tier, the has_mcp_app flag, the single prompt name adobe-marketing-agent-mcp-widget, and the client list of Claude, the Claude API and Claude Code). The connector's public directory page — https://claude.com/connectors/adobe-marketing-agent (fetched 2026-08-19) — publishes four example prompts, all of them data questions that map to no tool in the listing · retrieved 2026-08-16
Adobe support for this connector — https://helpx.adobe.com/enterprise.html (per the directory snapshot, 2026-08-16) · retrieved 2026-08-16