Adobe Target MCP server: activities, lift and offers in Claude, Codex or Cursor
Adobe Target reaches Claude, Codex or Cursor through the Agent Planners MCP endpoint with 6 reads and 3 writes of its own: activities and their lift by experience, offers, audiences and locations, and approval-gated offers, audiences and saved activities.
What already exists for Adobe Target
Adobe hosts an Adobe Target MCP server (targetmcp.adobe.io), in public beta and read-only during the beta as of November 2026, signed in with your Adobe ID.
Under any layer sits the Target Admin API on mc.adobe.io with your tenant in the path — and a different media type per resource.
What this setup adds
| Adobe's hosted server | Agent Planners MCP | |
|---|---|---|
| Writes | Read-only during the beta | JSON offers, audiences, saved activities and state changes under the key's write mode |
| Making an activity live | — | Held for a person on every key mode |
| Target tools | The server's own | 6 reads and 3 writes, plus two shared connection reads |
| Media types | Handled by the server | Set per path (offers v2, activities and audiences v3, the rest v1) |
How to configure it
- 1In Adobe Developer Console add the Adobe Target 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 Target card, press Paste JSON (or Manual entry) and Test connection. The card requests only this product's scopes:
openid,AdobeID,target_sdk,additional_info.projectedProductContext,read_organizations,additional_info.roles. - 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__target_list_activities.
# 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 Adobe Target tools
| Tool | Kind | What it does |
|---|---|---|
target_list_activities | Read | Target activities (GET activities): id, name, type (ab | xt | …), state (approved = live | deactivated | saved | archived), priority, startsAt / endsAt, modifiedAt. |
target_get_activity | Read | ONE activity with its locations, options, experiences and metrics (GET activities/ab/{id} or activities/xt/{id}). |
target_list_offers | Read | Offers (GET offers): id, name, type (content | json …), modifiedAt. |
target_list_audiences | Read | Target audiences (GET audiences): id, name, description, origin, modifiedAt. |
target_activity_report | Read | An activity's performance report (GET activities/ab/{id}/report/performance or xt): visitors, visits, conversions and lift per experience. |
target_get | Read | ANY Target Admin API GET under the tenant (path relative to /{tenant}/target/: activities[/ab|xt/{id}], offers[/content|json/{id}], audiences[/{id}], properties, mboxes, environments, reports …). |
target_set_activity_state | Write — always a person | Change an activity's state (PUT activities/state with the id): { accountId?, activityId, state: approved | deactivated | saved }. ★ approved (the activity goes LIVE on the site) is PERSON-GATED on every lane. |
target_create_offer | Write | Create an offer (POST offers/content or offers/json): { accountId?, name, type: html | json, content (an HTML fragment, or a JSON object / string) }. ★ An HTML offer is code that runs on the site — PERSON-GATED. |
target_mutate | Write | Any other Target Admin API write under the tenant (method POST | PUT | DELETE, path relative to /{tenant}/target/, body = Adobe's own fields; contentType? defaults to application/vnd.adobe.target.v3+json): activities … |
describe_tool on one of them says to connect the Adobe Target 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 — a JSON offer, an audience, an activity created saved, deactivating an activity — 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:
- An activity made live (state approved), directly or inside a gateway body.
- Any HTML or content offer — code that runs on the site.
- Any delete.
What we measured
- Offers accept v2 only, activities and audiences v3, mboxes / environments / properties v1 — a wrong one answered 415.
- The tenant was found from the organization's name with at most four probe reads; a wrong tenant answers 403 502061.
- An HTML offer created, changed, read back and deleted; an audience created and deleted; an A/B activity created saved, deactivated and deleted — never made live.
Frequently asked questions
- Is there an official Adobe Target MCP server?
- Yes: Adobe hosts one (targetmcp.adobe.io), in public beta and read-only during the beta as of November 2026. Agent Planners also changes Target — offers, audiences, activity state — with making an activity live always held for a person.
- 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.
- How do I connect Claude to Adobe Target?
- Connect Adobe Target on its card on Integrations (with your tenant), create an Agent Planners key, add the MCP server to Claude, and call adobe__target_list_activities.