Is there an MCP server for Adobe Launch?

Yes. Agent Planners runs a hosted MCP server at https://www.agentplanners.com/api/mcp that gives Claude, ChatGPT, Codex and other MCP clients 7 Adobe Launch read tools and 4 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 Launch MCP server: rules, data elements and libraries in Claude, Codex or Cursor

TL;DR

Adobe Launch reaches Claude, Codex or Cursor through the Agent Planners MCP endpoint with 7 reads and 4 writes of its own: properties, rules, data elements, extensions and libraries with their publishing state, and approval-gated rule switches and development libraries.

What already exists for Adobe Launch

Adobe Launch (now called Tags in Adobe Experience Platform) was not on Experience League's list of Adobe-hosted MCP servers in November 2026.

Under any layer sits the Reactor API (reactor.adobe.io, JSON:API): every change is a new revision, and nothing reaches a site until a library is built and published.

What this setup adds

Calling the Reactor API yourselfAgent Planners MCP
Launch toolsWhatever you write7 reads and 4 writes, plus two shared connection reads
Library adds after a change409 "needs to be revised"Revised and added with the new revision
Builds, publishing, custom code, extensionsSent when calledHeld for a person on every key mode
Other platformsLaunch onlyGoogle Tag Manager and every platform the workspace connected, on one endpoint

How to configure it

  1. 1In Adobe Developer Console add the Experience Platform Launch API API to a project with an OAuth Server-to-Server credential, and put the credential on the product profile it should use.
  2. 2On Integrations open the Adobe Launch card, press Paste JSON (or Manual entry) and Test connection. The card requests only this product's scopes: AdobeID, openid, read_organizations, additional_info.job_function, additional_info.projectedProductContext, additional_info.roles.
  3. 3Create a key in API & MCP: tools:read for reading, add tools:write for changes. To keep a key to Adobe, choose Only these platforms → Adobe.
  4. 4Add the server to your client with one of the snippets below, run describe_permissions, then adobe__get_connection and adobe__launch_list_rules.
bash
# 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}" } } } }
Launch also needs the IMS Organization ID (ends in @AdobeOrg) — it is in the project JSON. Every client's setup: MCP setup guide.

The Adobe Launch tools

ToolKindWhat it does
launch_list_companiesReadThe Tags (Reactor) companies the credential reaches (GET companies): id (CO…), name, org id.
launch_list_propertiesReadTags properties of the configured company (GET companies/{id}/properties): id (PR…), name, platform (web | mobile | edge), domains, enabled.
launch_list_rulesReadRules of a property (GET properties/{id}/rules): id (RL…), name, enabled, published, dirty, revision.
launch_list_data_elementsReadData elements of a property (GET properties/{id}/data_elements): id (DE…), name, delegate, enabled, published.
launch_list_extensionsReadInstalled extensions of a property (GET properties/{id}/extensions): id (EX…), name, display name, version, enabled.
launch_list_librariesReadLibraries of a property (GET properties/{id}/libraries): id (LB…), name, state (development | submitted | approved | rejected | published), build required, environment.
launch_getReadANY Reactor API GET (companies[/{id}], properties/{id}[/rules|data_elements|extensions|libraries|environments|hosts], rules/{id}[/rule_components], data_elements/{id}, libraries/{id}[/builds], builds/{id}, extension_p…
launch_create_libraryWriteCreate a development library in a property (POST properties/{id}/libraries): { accountId?, propertyId?, name, ruleIds?, dataElementIds?, extensionIds? (the resources to add) }.
launch_build_libraryWrite — always a personBuild a library (POST libraries/{id}/builds) — deploys it to the library's environment: { accountId?, libraryId }.
launch_set_rule_enabledWriteEnable or disable a rule (PATCH rules/{id} attributes.enabled — a new revision; it reaches the site only when a library with it is built and published): { accountId?, ruleId, enabled: true | false }.
launch_mutateWriteAny other Reactor write (method POST | PATCH | DELETE, path such as properties/{id}/rules, rules/{id}/rule_components, properties/{id}/data_elements, libraries/{id}/relationships/rules; body = JSON:API { data: { type,…
Each Adobe product is its own connection and its own MCP offering. A workspace that has connected Adobe Launch lists and finds its tools; one that has not does not list them at all, and describe_tool on one of them says to connect the Adobe Launch 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 development library, a rule switched on or off, settings that are not code — 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:

  • A library build and submit / approve / publish.
  • Custom code, and any rule-component or data-element settings change that could rewrite it.
  • Extensions, environments and hosts.
  • Any delete.
Refused outright: creating or removing a Launch company, batch bodies and credentials paths.

What we measured

  • 13 properties read on a real Launch company, with rules, data elements and libraries.
  • In a throwaway property: a data element created, renamed and deleted; a host; a development environment; a library with the Core extension; a build that succeeded. Nothing was published to a site.
More on Adobe Launch: what the agent does · setup and every tool · MCP server · AI agent guide · playbook. The other Adobe products, each its own connection: Adobe Analytics · Adobe Experience Platform · Adobe Target · All four together: Adobe.

Frequently asked questions

Is there an official Adobe Launch MCP server?
Not as of November 2026: Adobe Launch was not on Experience League's list of Adobe-hosted MCP servers. Agent Planners reaches the Reactor API with your own Server-to-Server credential.
Can an MCP client publish Launch changes?
It can ask; a build or a publish action is held for a person whatever the key's write mode.
Is Adobe Launch the same as Adobe Launch?
Yes — Adobe renamed Launch to Tags; the Developer Console API is still Experience Platform Launch API.
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