Skip to content
<- All docs

Managed MCP

Set Up Managed Amazon Ads MCP

Connect Managed Amazon Ads MCP to your AI client, authorize the right advertising account, confirm its scope and run a first read before campaign changes.

Updated Oct 22, 2026 3 min read

Managed Amazon Ads MCP connects your AI client to Amazon advertising operations while Kuudo operates the service. Use it for campaigns, bids, budgets, reporting, Amazon DSP (demand-side platform) and Amazon Marketing Cloud within your authorized account scope.

Obtain the managed connection

Start with the Managed MCP connection guide. Request access to this service and obtain its connection URL and authentication method. Add the supplied connection to your AI client. Keep service credentials in secure connection settings rather than ordinary chat messages.

Managed MCP and Private Cloud share the same ownership principles. The setup described here uses the service operated by Kuudo. For customer-cloud infrastructure, see Private Cloud.

Resolve the advertising account first

Authorize the intended advertising account, then confirm the advertiser, region and advertising profile or other account identifier required for the operation. Access to an advertising account does not establish access to every DSP advertiser or Amazon Marketing Cloud instance.

Verify a bounded first task

Use this request after connecting:

Show the advertising accounts this connection can access.
Confirm the account and marketplace before reading campaign performance.
Do not change campaigns, bids or budgets.

The response should identify the account context and distinguish a completed empty result from an access or processing error. For reports, retain the report identifier, dates, filters and attribution basis.

Continue with the product workflow

Campaign changes are a separate scoped action. Review the proposed operation and the approval policy before executing it. For recurring ingestion into a retained lake, use Agent Flow through Private Cloud.

See the product overview and shared usage reference for the supported workflow. To change where the service runs, follow Choose Managed MCP or Private Cloud.