Adobe Experience Platform MCP server: schemas, datasets and audiences in Claude, Codex or Cursor
Adobe Experience Platform reaches Claude, Codex or Cursor through the Agent Planners MCP endpoint with 5 reads and 2 writes of its own: sandboxes, XDM schemas, datasets and audiences, an Experience Platform read gateway, and approval-gated audiences and schema changes.
What already exists for Experience Platform
Adobe hosts MCP servers for Real-Time CDP (beta, by allowlist), Journey Optimizer and Customer Journey Analytics. Experience Platform's own schemas, datasets and sandboxes were not on Experience League's list of Adobe-hosted servers in November 2026.
Under any layer sits platform.adobe.io: every call carries the IMS organization and a sandbox, and the Schema Registry wants its own Accept headers.
What this setup adds
| Calling the API yourself | Agent Planners MCP | |
|---|---|---|
| Sandbox and headers | Set on every request | The connection's sandbox (or one a call names) and the right Accept per path |
| Experience Platform tools | Whatever you write | 5 reads and 2 writes, plus two shared connection reads |
| Ingestion, dataflows, destinations, merge policies | Sent when called | Held for a person on every key mode |
| Sandboxes, access control, privacy jobs | Reachable with the right profile | Refused on every lane |
How to configure it
- 1In Adobe Developer Console add the Experience Platform API API to a project with an OAuth Server-to-Server credential, and put the credential on the product profile it should use.
- 2On Integrations open the Adobe Experience Platform card, press Paste JSON (or Manual entry) and Test connection. The card requests only this product's scopes:
openid,AdobeID,read_organizations,additional_info.projectedProductContext,session. - 3Create a key in API & MCP:
tools:readfor reading, addtools:writefor changes. To keep a key to Adobe, choose Only these platforms → Adobe. - 4Add the server to your client with one of the snippets below, run
describe_permissions, thenadobe__get_connectionandadobe__aep_list_schemas.
# Claude Code
claude mcp add --transport http agent-planners https://www.agentplanners.com/api/mcp \
--header "Authorization: Bearer $AGENTPLANNERS_API_KEY"
# Codex (signs in with OAuth in the browser)
codex mcp add agent-planners --url https://www.agentplanners.com/api/mcp
# Cursor (~/.cursor/mcp.json)
{ "mcpServers": { "agent-planners": { "url": "https://www.agentplanners.com/api/mcp", "headers": { "Authorization": "Bearer ${env:AGENTPLANNERS_API_KEY}" } } } }The Experience Platform tools
| Tool | Kind | What it does |
|---|---|---|
aep_list_sandboxes | Read | The Experience Platform sandboxes this credential reaches (GET data/foundation/sandbox-management/): name, title, type (production | development), default, region. |
aep_list_schemas | Read | XDM schemas in the connection's sandbox (GET data/foundation/schemaregistry/tenant/schemas, or global with container:"global"): $id, title, meta:class, version. |
aep_list_datasets | Read | Datasets in the sandbox (GET data/foundation/catalog/dataSets): id, name, schemaRef, tags, created, last batch. |
aep_list_audiences | Read | Audiences (segment definitions) in the sandbox (GET data/core/ups/segment/definitions): id, name, expression (PQL), evaluation (batch | streaming | edge), merge policy, status. |
aep_get | Read | ANY Experience Platform API GET (path starting data/: data/foundation/catalog/…, data/foundation/schemaregistry/…, data/core/ups/…, data/foundation/flowservice/…, data/foundation/identity/…). |
aep_create_audience | Write | Create an audience (segment definition) in the sandbox (POST data/core/ups/segment/definitions): { accountId?, name, description?, expression (PQL — e.g. homeAddress.country = "US"), mergePolicyId?, evaluation? (batch… |
aep_mutate | Write | Any other Experience Platform write (method POST | PUT | PATCH | DELETE, path data/…, body = Adobe's own fields): schemas, field groups, datasets, audiences, identity namespaces, tags. ★ DELETE, data ingestion (data/f… |
describe_tool on one of them says to connect the Adobe Experience Platform card. A key narrowed to the Adobe platform reaches only the Adobe products the workspace has connected; adobe__get_connection shows each one.What waits for a person, whatever the key allows
Ordinary writes — an audience, a schema, a field group — run inside the workspace's guardrails or queue for an admin, as the key was minted. These are held for a person on every key mode:
- Data ingestion (data/foundation/import) and dataflows and destinations (flow service — activating an audience is one).
- Merge policies, Profile system jobs and Query Service statements.
- Any delete.
What we measured
- The sandbox list 404s without its trailing slash; Schema Registry answered 400 to a plain JSON Accept. Both are set for you.
- A schema was created, patched, read back and deleted; a field group created and deleted.
- Datasets 403 without Data Management; audiences and merge policies 401 "RBAC Unauthorized" without Profile Management — the tools name the permission.
Frequently asked questions
- Is there an official Adobe Experience Platform MCP server?
- Not for Experience Platform's schemas, datasets and sandboxes as of November 2026; Adobe hosts MCP servers for Real-Time CDP (beta, allowlist), Journey Optimizer and others. Agent Planners reaches Experience Platform with your own Server-to-Server credential.
- Can an MCP client activate an audience?
- It can ask; activation is a dataflow, which is held for a person whatever the key's write mode.
- Which sandbox does it use?
- The connection's sandbox, or another one the credential reaches when a call names it.