# Set Up Managed Amazon Ads MCP

Canonical page: https://www.kuudo.com/docs/managed-mcp/amazon-ads/


The Amazon Ads MCP connects an MCP-compatible AI client to advertising accounts authorized in your Kuudo organization. Depending on your Amazon permissions and the available tools, you can explore accounts and campaigns, retrieve performance information, and work with advertising operations.

## Endpoints and sign-in

| Purpose                  | Address                                                          |
| ------------------------ | ---------------------------------------------------------------- |
| MCP server               | `https://ads.kuudo.com/mcp`                                      |
| OAuth resource discovery | `https://ads.kuudo.com/.well-known/oauth-protected-resource/mcp` |
| Kuudo sign-in issuer     | `https://app.kuudo.com`                                          |

Add the **MCP server** address to your client. The other addresses are used by clients for OAuth discovery; you normally do not enter them manually.

Authentication uses OAuth with your **Kuudo user account**. During sign-in, choose the Kuudo organization that contains the Amazon Ads authorization and approve the permissions shown. The client manages the resulting access token. Your Amazon authorization is a separate connection that permits Kuudo to work with the Amazon Ads account; signing in to Kuudo alone does not create it.

The server's published access scopes include `mcp:access`, `amazon-connections:read`, and `amazon-tokens:vend`. Review the permissions shown in Kuudo's consent screen.

A successful sign-in is not proof that a particular client can discover or use every tool. Confirm the connection and account access with a read-only request.

## Before you connect

- Have a Kuudo user account and membership in the intended organization.
- In Kuudo, open **Authorizations**, select **Connect Amazon**, choose **Amazon Ads** and the appropriate region, and complete Amazon's consent flow. To request an account owner’s approval, [send an external invitation](/docs/invite-amazon-account-owner/). See [Connect and Manage Amazon Authorizations](/docs/amazon-authorizations/).
- Use an MCP client that supports remote HTTP connections and Kuudo's OAuth flow. For client compatibility, see [OAuth client requirements](#oauth-client-requirements).

## Connect your AI client

1. In the client, add a remote MCP server or custom connector.
2. Enter `https://ads.kuudo.com/mcp` as the server URL.
3. Start the connection. When prompted, sign in with your Kuudo user account, select the intended organization if asked, and approve the requested access.
4. Confirm that the client shows the server as connected and lists its tools. Select an authorized Ads account or profile when your client or the requested operation asks for one.
5. Try a read-only request, such as: “List the Amazon Ads profiles I can access.” Confirm that the results are for the expected account and region before making changes.

The client may ask you to approve individual actions. Review account, marketplace, and campaign details before allowing any operation that changes Amazon data.

## Reporting API v1

The Amazon Ads MCP supports Amazon's new Reporting API v1, including report creation and retrieval through `allv1_AdsApiv1CreateReport` and `allv1_AdsApiv1RetrieveReport`. Report generation is asynchronous: creating a job returns an identifier; retrieve it until it completes or fails, then download every returned report part.

The [Amazon Ads Reporting Skill](/features/skills/amazon-ads/reporting/) adds premade SP, SB and SD report definitions, account-context checks, custom-field validation and the retrieval workflow. Install the Skill in a compatible AI client and connect the Ads MCP for live operations. For the available templates, a reusable reporting request and migration checks, see [Amazon Ads Reporting API v1: Automate Reports](/guides/amazon-ads-reporting-api-v1/).

## OAuth client requirements

Kuudo supports OAuth authorization code with PKCE and client ID metadata documents (CIMD), as well as appropriately preregistered clients. A client that supports only dynamic client registration needs an appropriate Kuudo registration. Client support and setup labels vary; check your client's documentation if sign-in does not start.

## Troubleshooting

- **Sign-in succeeds but the client cannot discover tools:** Reconnect and check the client error. A completed browser sign-in alone does not confirm the MCP connection. Contact support with the time and client name if the problem continues; do not share tokens.
- **No Ads accounts appear:** Check the selected Kuudo organization, the Ads authorization and its region, and the Amazon user's access to the intended account.
- **A tool is unavailable or an operation is denied:** Availability depends on the connected Amazon account, permissions, region, and client. Check the error and the account selected.
- **You selected the wrong organization:** Disconnect and reconnect, then select the intended organization during Kuudo sign-in.