Claude connects to Amazon Ads through the Kuudo Amazon Ads MCP server, which turns Amazon Ads API operations into tools Claude can call. Add the server's signed connector URL as a custom connector in Claude, switch it on in a chat, and tell Claude which advertising profile to work in. Claude then answers from your live campaigns instead of an exported report.
Writes stay inside the Amazon Ads authorization you grant and your workspace policy, and the packaged Skills keep campaign changes as proposals until you approve them. The steps below work for Claude on the web and Claude Desktop. For Claude Code, use the Claude Code quick start.
Your MCP server hostname is private to your deployment. Replace {your-private-mcp-host} with the private host shown in your dashboard.
What can Claude do with Amazon Ads?
Once connected, Claude works on the advertising account through Amazon's own Ads API, reads and approved writes alike:
- Sponsored ads: Sponsored Products, Sponsored Brands and Sponsored Display campaigns, ad groups, keywords, targets, bids and budgets.
- Reporting: request Amazon Ads reports and read them back. Amazon builds each report asynchronously and decides how long it takes.
- Amazon DSP (demand-side platform): campaigns for the DSP advertisers your account can reach.
- Amazon Marketing Cloud (AMC): SQL workflows and audiences in the AMC instances your account can reach.
- Accounts and billing: advertising profiles, manager accounts, portfolios and account budgets.
Every tool is listed in the Amazon Ads API tools reference, and the Amazon Ads MCP page covers the server.
What you need before connecting Amazon Ads to Claude
- A Kuudo workspace with the Amazon Ads MCP server deployed, and access to its dashboard.
- Your Amazon Ads account authorized in Kuudo. On Kuudo Pro and Kuudo Scale, the account owner consents once to Kuudo's managed Amazon Ads app with Login with Amazon, or an agency sends its client an authorization invitation. On Kuudo Community you connect your own Amazon app. See Amazon account authorization.
- Claude on the web or Claude Desktop. Custom connectors work on every Claude plan, but Free allows only one. Connecting Seller Central or Vendor Central beside Amazon Ads needs Pro, Max, Team or Enterprise.
- On Team and Enterprise, an Owner adds the connector first under Organization settings > Connectors, and members then connect to it.
Connect Amazon Ads to Claude
1. Copy the Amazon Ads connector URL
In your Kuudo dashboard, open the Keys tab, create a key if needed, and copy the Claude connector URL for the Amazon Ads MCP server. The URL is already signed for Claude, so your API key never goes into Claude:
https://{your-private-mcp-host}/mcp/connect/{signed-token}Claude's connector form takes a single URL and cannot attach an Authorization header, which is why it needs the signed URL rather than the plain /mcp endpoint.
2. Add it as a custom connector
- In Claude, open Customize > Connectors.
- Click +, then Add custom connector.
- Name it
amazon-ads, so it stays easy to tell apart from a Seller Central connector. - Paste the signed URL and click Add.
3. Switch it on in a chat
Start a new chat, open Connectors from the composer and switch amazon-ads on. When Claude asks to use a tool, read the request: choose Allow always only for read tools you trust, and keep tools that change bids, budgets or campaign state on ask.
4. Check the connection with a read-only question
Ask a question that reads your Amazon Ads data without changing anything:
Which Amazon Ads accounts and profiles can you reach? Don't change anything.Claude should list each advertising account with its marketplace profiles. An empty list means the connector works but no Amazon Ads account is authorized yet; see the troubleshooting below.
Choose the advertising profile Claude works in
Nearly every Amazon Ads operation is scoped to one advertising profile, and a profile covers one marketplace, so a single advertiser often has several: US, UK and Germany, for example. Tell Claude which one to use, by country or by name:
Use our UK profile for the rest of this chat.With the Kuudo Skills added to Claude (Claude app Skills quick start), the Amazon Ads Accounts Skill handles this step. It lists the accounts and profiles your authorization reaches, asks you to choose when more than one fits, and keeps the choice for the session. It only reads, and never creates or links an account. Profiles in every marketplace your advertising account reaches, across North America, Europe and Asia-Pacific, are available. An agency sees every authorized client account from the same connector, so name the client as well as the country.
First Amazon Ads tasks to try in Claude
- A performance report: "Pull last week's Sponsored Products performance by campaign for the US profile." The Amazon Ads reporting Skill sets the report's fields, ad product and grain before Amazon builds it.
- Search-term mining: "Mine the last 30 days of Sponsored Products search terms and propose negatives. Don't apply anything." See Mine Sponsored Products Search Terms.
- A structure audit: "Audit our Sponsored Products campaign structure." See Audit Sponsored Products Campaign Structure.
- Budget pacing: "How is this month's spend pacing against plan?" Pace Amazon Ads Budgets to Plan returns budget changes as a proposal you approve.
Troubleshooting Amazon Ads in Claude
Claude lists no Amazon Ads profiles
The connector works, but no Amazon Ads account is authorized for your workspace yet. Authorize the account in Kuudo, or send its owner an invitation, then ask again.
A marketplace is missing
Profiles exist per marketplace. When one country is missing, either the advertiser has no profile there or that account is not authorized yet.
The custom connector will not add
Use the signed Claude connector URL from the Keys tab, not the plain /mcp endpoint. Claude's form cannot send an Authorization header.
Unauthorized or 401 errors
Create a fresh key in the Keys tab, copy a new signed connector URL, and replace the connector in Claude.
A report is still pending
Amazon builds Amazon Ads reports asynchronously and decides how long each one takes and whether it completes. Ask Claude to check the report's status later rather than requesting it again.
Frequently asked questions
Can Claude change my Amazon Ads campaigns?
Yes. The Amazon Ads MCP includes write tools for bids, budgets, targets and campaign state, and they act only inside the Amazon Ads authorization you grant and your workspace policy. Claude asks before it calls a tool unless you chose Allow always, and the packaged Skills keep changes as proposals until you approve them.
Does it work with Amazon DSP and Amazon Marketing Cloud?
Yes. Amazon DSP (demand-side platform) and Amazon Marketing Cloud (AMC) operations are part of the same Amazon Ads MCP server, so Claude can work with the DSP advertisers and AMC instances your authorized account reaches in Amazon, from the same connector.
Can an agency connect its clients' Amazon Ads accounts?
Yes. The agency sends each client an authorization invitation, the client consents once without sharing a login, and every authorized account is then reachable from the same Claude connector. Name the client and the country when you choose a profile.
Does Amazon have its own MCP server for Amazon Ads?
Yes. Amazon's Ads MCP Server is available in open beta to Amazon Ads partners with active API credentials, authorized through your own Login with Amazon application. Kuudo connects through its managed Amazon Ads app on Pro and Scale and runs in your own cloud. See Kuudo vs the Amazon Ads MCP Server.
Can I connect Amazon Ads on Claude's free plan?
Yes, as your one custom connector. Anthropic limits the Free plan to one custom connector, so adding Seller Central or Vendor Central beside Amazon Ads needs Claude Pro, Max, Team or Enterprise.
Related
- Connect your Amazon accounts to Claude: the Claude setup for every Kuudo server.
- How to connect Amazon Seller Central to Claude and How to connect Amazon Vendor Central to Claude.
- How to connect Amazon Ads to ChatGPT.
- Anthropic's guide to custom connectors using remote MCP.