Adovo

Adobe Experience Cloud

Adobe Marketing Agent MCP works locally but rejects a hosted OAuth callback

Separate local OAuth success from hosted callback approval when deploying an Adobe Marketing Agent MCP client.

November 9, 2026

A local MCP client authenticates, but the hosted deployment cannot register its callback. A November 6 Experience League question reports 400 invalid_redirect_uri from Adobe Marketing Agent MCP registration for two HTTPS callbacks while localhost succeeds. There was no answer when this draft was researched. Local success therefore cannot be treated as proof that production onboarding is ready.

Identify the blocked boundary

Record the exact redirect URI sent at registration and the returned error, with secrets removed. Check scheme, hostname, path, trailing slash and environment-specific callback before changing code. Keep development and production callbacks distinct. A registration error happens before a customer's marketing data is accessed, so increasing data scopes is not a sensible first response.

Adobe's general user authentication guide describes application credentials and authorized redirect URIs. It does not document a Marketing Agent MCP policy for dynamic client registration on hosted domains. Adobe's AI registry confirms the Marketing Agent connector exists, but it also does not resolve this callback approval question.

Plan the customer rollout around an answer

Before promising a launch date, ask Adobe which registration or administrator approval path supports the intended hosted callback model. Include whether each customer needs a separate application and who owns its lifecycle. Request a documented test with one non-production tenant, then verify the complete authorization flow and token refresh. Preserve the localhost proof only as a diagnostic baseline.

If Adobe requires a different supported connection pattern, update the onboarding design before inviting customers. Do not build an undocumented redirect workaround into a shared production client.

Adovo’s view

An integration is not production-ready because it works on a laptop. The hard part is the customer boundary: who authorizes the client, which callback is trusted, and how that trust survives a new tenant. Get that contract in writing before scaling the connector.

Continue exploring

Adobe Experience Cloud

Adobe Experience ManagerMCP

An AEM MCP connection needs three access checks

Check client authorization, AEM user permissions, and environment traffic rules before treating an AEM MCP failure as a tool defect.

Read more

Adobe Experience Cloud

Adobe WorkfrontCX Coworker

Workfront Coworker write access needs a live approval test

A Workfront MCP write toggle alone does not prove Coworker can update a real issue or parse IDs from a CSV.

Read more

Adobe Experience Cloud

Adobe Journey OptimizerMigration

AJO onboarding can convert assets, but migration still needs acceptance tests

Evaluate AJO guided onboarding with a representative migration slice and explicit review gates.

Read more
Explore Adobe services →