Install Adobe CX Coworker Gateway mcp-install

Read this guide to learn how to connect an MCP-compatible client to Adobe CX Coworker Gateway. CX Coworker Gateway uses one endpoint for all documented product tools:

https://cx-coworker-gateway.adobe.io/mcp

Before installing, confirm that your organization and user account can access the product tools you need. See Access CX Coworker Gateway tools.

How installation works mcp-install-how

CX Coworker Gateway uses a remote HTTP transport with a browser-based Adobe sign-in flow. In every supported client, the setup pattern is the same:

Enterprise installation (admin-managed) mcp-install-enterprise

Most team and enterprise MCP client plans require an administrator to add custom connectors for the organization. In these environments, installation has two steps:

Step 1: An administrator adds the endpoint mcp-install-enterprise-admin

The administrator adds https://cx-coworker-gateway.adobe.io/mcp as a custom connector or remote MCP server in the client’s organization settings. The exact location depends on the client.

Claude Team and Enterprise mcp-install-enterprise-claude

In Claude Team and Enterprise plans, organization-level connectors are managed by a workspace Owner or Primary Owner.

ChatGPT Team and Enterprise mcp-install-enterprise-chatgpt

In ChatGPT Team and Enterprise workspaces, connectors are added by a workspace administrator.

Other organization-managed clients mcp-install-enterprise-other

For other clients that support organization-managed remote connectors, add CX Coworker Gateway as a remote HTTP MCP server using https://cx-coworker-gateway.adobe.io/mcp. Leave optional headers, bearer token fields, client ID fields, and client secret fields empty unless your client requires a placeholder value.

Step 2: Users enable the connector mcp-install-enterprise-user

After an administrator adds CX Coworker Gateway, each user enables it for their own account:

Users do not need to enter the URL themselves when an administrator has already added the connector for the organization.

Individual installation (self-service) mcp-install-individual

If you use an individual plan, a locally configured developer client, or an organization that allows members to add their own connectors, add the endpoint directly in your own client settings.

Claude individual mcp-install-individual-claude

For claude.ai and Claude Desktop on an individual plan:

ChatGPT individual mcp-install-individual-chatgpt

Cursor mcp-install-individual-cursor

After connection, entitled Adobe for CX Coworker Gateway tools are available in Cursor’s Composer and Agent modes.

Claude Code mcp-install-individual-claude-code

Add the endpoint from the terminal:

claude mcp add --transport http cx-enterprise https://cx-coworker-gateway.adobe.io/mcp

Then start Claude Code and run:

/mcp

Select the cx-enterprise server and complete the Adobe sign-in flow in your browser.

Codex mcp-install-individual-codex

Add the endpoint from the terminal:

codex mcp add cx-enterprise --url https://cx-coworker-gateway.adobe.io/mcp

Authenticate:

codex mcp login cx-enterprise

Verify the configuration:

codex mcp list

You can also add the endpoint directly to ~/.codex/config.toml:

[mcp_servers.cx-enterprise]
url = "https://cx-coworker-gateway.adobe.io/mcp"

General JSON configuration mcp-install-individual-json

For clients that accept a JSON-based MCP server configuration, use one of the following formats depending on whether your client supports native remote HTTP or requires a local bridge.

Via mcp-remote bridge

{
  "mcpServers": {
    "cx-enterprise": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://cx-coworker-gateway.adobe.io/mcp"
      ]
    }
  }
}

Native remote HTTP

{
  "mcpServers": {
    "cx-enterprise": {
      "url": "https://cx-coworker-gateway.adobe.io/mcp",
      "transport": "http"
    }
  }
}

Other clients mcp-install-individual-other

For other desktop or web clients with remote MCP support, add Adobe for CX Coworker Gateway as a remote HTTP server using https://cx-coworker-gateway.adobe.io/mcp. Leave optional headers, bearer token fields, client ID fields, and client secret fields empty unless your client requires a placeholder value.

Product context for tool calls mcp-connect-params

The MCP scopes every tool call to one active Adobe organization. Beyond that, context requirements depend on the product:

Set context once at the start of a session — individual product tools do not switch organizations, sandboxes, or data views mid-session. See Session context tools for the tools that set organization, sandbox, and data view context.

Example:

“Use organization 1234ABCD@AdobeOrg, sandbox prod, and data view My Company — Global for this session.”

If you do not know the required values, ask your MCP client to list the organizations, sandboxes, or data views available to your Adobe credentials.