Is there an MCP server for Adobe?

Yes. Agent Planners runs a hosted MCP server at https://www.agentplanners.com/api/mcp that gives Claude, ChatGPT, Codex and other MCP clients 28 Adobe read tools and 13 write tools. Sign in with OAuth or an API key. Writes follow your approval settings; changes you can't take back wait for a person unless an admin exempts a key.

MCP

Adobe MCP server: Analytics, Target, Experience Platform and Launch in Claude, Codex or Cursor

TL;DR

Adobe now hosts MCP servers of its own for several products (Analytics, Target in beta, Journey Optimizer, Real-Time CDP and more), each signed in with your Adobe ID. This guide covers a different setup: your own OAuth Server-to-Server credential connected once per product, the token kept on our server, one adobe family over MCP that also reaches Experience Platform's schemas and Launch (which Adobe's hosted list does not include), and the same approvals as in the app.

Each Adobe product's own MCP guide

Each product is its own connection and its own MCP offering: a workspace lists and finds only the Adobe products it connected. The product guides have each one's tools, setup and limits:

What already exists for this platform

Adobe's Experience League lists Adobe-hosted MCP servers, among them Adobe Analytics (aa-mcp.adobe.io), Adobe Target (targetmcp.adobe.io — public beta, read-only while in beta), Customer Journey Analytics, Journey Optimizer, Real-Time CDP (beta, allowlist) and Marketo Engage. They sign in with Adobe IMS as the person using them, and what each can do depends on the organization's entitlements and that person's permissions. Experience Platform itself (schemas, datasets, sandboxes) and Adobe Launch are not on that list (checked November 2026).

Under any MCP layer sit the products' own developer APIs, each with its own host and headers: analytics.adobe.io (with the company id), platform.adobe.io (with the IMS organization and a sandbox), mc.adobe.io (with the Target tenant) and reactor.adobe.io (JSON:API).

  • Scopes do not grant access. What a credential may read or change is decided by its product profiles in Adobe Admin Console; a valid token can still be refused per resource.
  • IMS accepts scopes it does not know (measured): a token proves nothing about a product — each product needs its own read before it is called connected.
  • Going live is a separate step. A Target activity serves when its state is approved; a Launch change reaches a site only when a library is built and published.

What a hosted layer adds

Adobe's hosted serversAgent Planners MCP
ProductsAnalytics, Target (beta), CJA, AJO, Real-Time CDP and more — one server eachAnalytics, Experience Platform, Target, Launch on one endpoint, beside every other platform the workspace connected
Sign-inEach person with their Adobe IDOne OAuth Server-to-Server credential per product, connected once by an admin or editor
Adobe toolsEach server's own28 reads, 13 writes
Target writesRead-only during the betaOffers, audiences and activity state — making an activity live waits for a person
Launch buildsNot listedA library build waits for a person; a rule's switch and a new library are ordinary changes
Approvals and auditAdobe's ownThe workspace's: approval queue, emailed approvers, Forbidden Rules, the audit log
Counted from the tool registry (src/lib/adobe/registry.ts). Over MCP the names are adobe__<tool>, for example adobe__analytics_report, adobe__target_list_activities, adobe__aep_list_schemas, adobe__launch_list_rules. A key that lists tools on demand reaches them through search_tools and call_tool.

How to configure it

  1. 1In Adobe Developer Console open your project, add the API of each product you want (Adobe Analytics, Experience Platform, Adobe Target, Experience Platform Launch API) with an OAuth Server-to-Server credential, and assign the product profiles the agent should have.
  2. 2On Integrations, each Adobe product has its own card. Press Paste JSON (the project's JSON download) or Manual entry, then Test connection — one product at a time, each with only its own scopes. The same project JSON works on every card.
  3. 3Pick what the product needs: the Analytics company, the Platform sandbox, the Target tenant (found by probing the organization's names when it can be), the Launch company and property.
  4. 4Create a key in API & MCP: tools:read for reading, add tools:write for changes. Add the server with the snippet below, run describe_permissions, then adobe__get_connection to see each product's connection.
bash
claude mcp add --transport http agent-planners https://www.agentplanners.com/api/mcp \
  --header "Authorization: Bearer ap_live_…"
Every client's setup, including OAuth sign-in without a key: MCP setup guide · Every tool and which product-profile permission unlocks what: Adobe guide.

What waits for a person, whatever the key allows

A tools:write key's ordinary Adobe writes — a segment, a calculated metric, a JSON offer, a schema, a new Launch library, a rule switched on or off — either run inside the workspace's guardrails or queue for an admin, depending on how the key was minted. These never run on the key's say-so: they are held in the approval queue, an admin or editor is emailed, and none is ever taken by a bulk approval.

  • A Target activity set live (state approved), directly or through the gateway.
  • An HTML offer — it is code that runs on the site.
  • A Launch library build, a publish action, custom code, an extension, an environment or a host.
  • Experience Platform ingestion, dataflows and merge policies, and Analytics classifications.
  • Every delete.
Refused outright on every lane: sandboxes, access control, privacy jobs, Analytics data repair, users, and any secrets or credentials path.

What we measured with a real Adobe organization

  • Report suites come from the product profile. With no report suite granted, the suite list answers 0 and a suite's reads answer 403 — the tools name the suites the organization's segments mention and the Admin Console steps. With "Analytics Admins" (auto-include) the same credential listed 14.
  • Totals are Adobe's, not a sum of rows. 30 daily rows of visits summed to 317,464 while Adobe's own total was 316,068 (a visitor on two days is one visit each day, one in the period): the report says to quote the totals.
  • Each Target resource has its own media type — offers v2 only, activities and audiences v3, the rest v1 — and Experience Platform's Schema Registry wants its own Accept header. Both are set per path; a wrong one answered 415 / 400.
  • A Launch library add needs the current revision. A resource changed since its revision answered 409 "needs to be revised"; the tool revises it and adds the new revision.
  • What the product profile still decides: datasets (Data Management), audiences and merge policies (Profile Management) and Query Service answered 403 / 401 until those permissions were added — the tools say which.
End to end, every read of the four products plus create → change → read back → delete of an Analytics segment and calculated metric, a Platform schema and field group, a Target offer, audience and saved (never live) activity, and a Launch data element, host, environment, library and build in a throwaway property. Never run live: a Target activity going live, a Launch publish to a site.

Frequently asked questions

Is there an official Adobe MCP server?
Yes, several: Adobe hosts MCP servers for Adobe Analytics, Adobe Target (public beta, read-only while in beta), Customer Journey Analytics, Journey Optimizer, Real-Time CDP and others, each signed in with your Adobe ID. Experience Platform's schemas and Adobe Launch are not among them (November 2026). Agent Planners reaches all four products with your own Server-to-Server credential on one endpoint, with its approvals.
How do I connect Claude to Adobe Analytics?
Connect Adobe Analytics on its card on Integrations with your Server-to-Server credential, create an Agent Planners key in API & MCP, add the MCP server to Claude, and call adobe__analytics_list_report_suites. No suites? Grant them in the credential's Analytics product profile.
Can an MCP client make a Target activity live?
It can ask; the change is held for a person, whatever the key's write mode. Offers, audiences and saved activities are ordinary changes.
Can it publish Adobe Launch changes to my site?
Not on its own. Creating a library and switching a rule are ordinary changes; a build, a publish action, custom code and extensions wait for a person.
Put a human-approved agent on your ad ops

Start free — 2,500 credits a month, no credit card. Reads run at once; by default every write waits for your approval.

Related reading