Connect
Adobe Launch: connect a company, permissions and tools
TL;DR
Adobe Launch connects on its own Integrations card with an OAuth Server-to-Server credential, your IMS Organization ID and a Launch company; property rights in the credential's product profile decide what the agent can read, change or build.
Before you start (in Adobe)
- 1Open Adobe Developer Console (developer.adobe.com/console), pick your organization, and open a project (or Create new project).
- 2Add API → Experience Platform Launch API (this is Tags), choose OAuth Server-to-Server, and tick the product profile the agent should use.
- 3In Adobe Admin Console → Adobe Experience Platform Data Collection → the profile, grant Property Rights on the properties; Develop / Publish rights let a person-approved build run.
- 4Copy the Organization ID (ends in
@AdobeOrg) with the Client ID and secret, or press Download for Project JSON.
Connect
- 1Integrations → Adobe Launch → Connect → Paste JSON (or Manual entry: name, Client ID, secret, IMS Organization ID).
- 2Test connection reads
GET /companies— the Launch companies the credential reaches. - 3Pick the Launch company and, optionally, a default property (PR…), then Save connection. A tool can name another property.
Scopes are added for you:
AdobeID, openid, read_organizations, additional_info.job_function, additional_info.projectedProductContext, additional_info.roles.Which permissions unlock what
- Property Rights: rules, data elements, extensions and libraries of that property.
- Develop / Publish: building, submitting, approving and publishing a library — each of which waits for a person here.
- Company Rights: properties, environments and hosts.
Every Adobe Launch tool
7 reads and 4 writes, plus get_connection and test_connection shared by the four Adobe products.
| Tool | Kind | What it does |
|---|---|---|
launch_list_companies | Read | The Tags (Reactor) companies the credential reaches (GET companies): id (CO…), name, org id. |
launch_list_properties | Read | Tags properties of the configured company (GET companies/{id}/properties): id (PR…), name, platform (web | mobile | edge), domains, enabled. |
launch_list_rules | Read | Rules of a property (GET properties/{id}/rules): id (RL…), name, enabled, published, dirty, revision. |
launch_list_data_elements | Read | Data elements of a property (GET properties/{id}/data_elements): id (DE…), name, delegate, enabled, published. |
launch_list_extensions | Read | Installed extensions of a property (GET properties/{id}/extensions): id (EX…), name, display name, version, enabled. |
launch_list_libraries | Read | Libraries of a property (GET properties/{id}/libraries): id (LB…), name, state (development | submitted | approved | rejected | published), build required, environment. |
launch_get | Read | ANY 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_library | Write | Create a development library in a property (POST properties/{id}/libraries): { accountId?, propertyId?, name, ruleIds?, dataElementIds?, extensionIds? (the resources to add) }. |
launch_build_library | Write — always a person | Build a library (POST libraries/{id}/builds) — deploys it to the library's environment: { accountId?, libraryId }. |
launch_set_rule_enabled | Write | Enable 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_mutate | Write | Any 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,… |
Over MCP and the REST API the names are adobe__<tool> (for example
adobe__launch_list_rules). A workspace with no connection for this product does not list these tools over MCP; describe_tool names the card to connect. Setup for Claude, Codex or Cursor: MCP server guide.Formats and limits
- The Reactor API is JSON:API (
application/vnd.api+json;revision=1); lists page withpageSize(≤ 100) andpage. - A rule switch is a new revision: it reaches the site only when a library with it is built and published.
- Adding a resource to a library needs its current revision — the tool revises a changed resource (Adobe's 409 "needs to be revised") and adds the new revision.
Changes and approvals
- Ordinary changes follow the approval setting — by default each waits for your approval: a development library, a rule switched on or off, a rule or data element whose settings show they are not code.
- A person approves, every time: a library build (
launch_build_library), submit / approve / publish, custom code and any rule-component or data-element settings change that could rewrite it, extensions, environments, hosts and any DELETE. - Refused on every lane: creating or removing a Launch company, a body carrying a batch of operations, and credentials paths.
Manage the connection
- Test again re-checks this product with one read-only request and stores the result.
- Configure changes this product's details; Replace credential swaps a rotated secret in place (cached tokens are dropped).
- Disconnect deletes the stored credential and its tokens here. It does not revoke the credential in Adobe — do that in Developer Console.
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 Adobe Launch the same as Adobe Launch?
- Yes. Adobe renamed Launch to Tags (Experience Platform Data Collection); the Developer Console API is still called Experience Platform Launch API, and its host is reactor.adobe.io.
- Can the agent publish to my site?
- Not on its own: building, submitting, approving or publishing a library waits for a person every time.
- Why did adding a rule to a library answer 409?
- The rule changed since the revision named. The tool revises it and adds the new revision; you see the revised id in the result.