OpenAI Ads Reporting
Enable AI agents such as Claude, Co-Pilot, Codex, and other compatible tools to create, manage, and optimize advertising campaigns on ChatGPT.Read full description
HYPD-AILABSCO SUMMARY
The workflow tools are the reason this exists rather than a REST client.
Launching Sponsored Products normally means three API calls in the right order with the right identifiers threaded between them — exactly the sequence an agent gets wrong. Bundling campaign, ad group and ad into one tool removes that failure mode, and the multi-country expansion does the same at a larger scale. This is partner-gated: without existing Amazon Ads API credentials there is nothing to connect.
What it is
Amazon Ads runs this one, announced as a global open beta for partners holding valid API credentials. Alongside the direct campaign and reporting calls it ships prepared workflow tools that bundle several steps into one.
What you get
- Campaign create, update and delete, plus performance and reporting queries
- Account-level settings and access to billing and financial data
- Workflow tools: account creation, report generation, campaign launch
- A single Sponsored Products workflow that creates the campaign, ad group and ad together
- Expansion into several countries from one prompt
Requirements
Status as an Amazon Ads partner with valid API credentials. The endpoint is regional — https://advertising-ai.amazon.com/mcp for North America, advertising-ai-eu.amazon.com for Europe and advertising-ai-fe.amazon.com for the Far East — and clients sign in over OAuth with a Login with Amazon client ID, or send a Login with Amazon access token and the client ID as request headers.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Launching Sponsored Products in one step
One workflow tool creates the campaign, ad group and ad together instead of three calls that must line up.
02
Taking a campaign into more countries
Expand to several marketplaces from a single prompt rather than repeating the setup per country.
03
Pulling performance without the console
Query reporting and billing directly while reviewing spend.
BEFORE YOU INSTALL
What to know first
Requires
Amazon Ads partners with active API credentials
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://advertising-ai.amazon.com/mcpRequirements
- OAuth 2.1 via Login with Amazon (Client ID from LwA security profile; callback URL must be added to Allowed Return URLs)
- Or token headers: Amazon-Ads-ClientId + Authorization: Bearer <YOUR_LW_ACCESS_TOKEN>
MCP Clients
Claude Code — OAuth Public Client
Sign in at developer.amazon.com, open Login with Amazon under your application settings, then your Security Profile → Web Settings.
Under Allowed Return URLs, add http://localhost:<YOUR_PORT>/callback with a fixed port such as 8001, and save.
Add the server as a public client, using the same port:
CLAUDE CODE — OAUTH PUBLIC CLIENT · TERMINAL
claude mcp add --transport http amzn-ads-mcp https://advertising-ai.amazon.com/mcp --client-id <YOUR_CLIENT_ID> --callback-port <YOUR_CALLBACK_PORT>For a private client, add --client-secret to that command; you will be prompted for the secret.
To authenticate, run claude, type /mcp, choose amzn-ads-mcp, and select Authenticate.
Claude Desktop — OAuth
In your Login with Amazon Security Profile (Web Settings), add https://claude.ai/api/mcp/auth_callback to Allowed Return URLs.
Go to Customize > Connectors.
Click the plus sign and choose Add custom connector.
Enter the server name (e.g., Amazon Ads MCP) and the server URL (https://advertising-ai.amazon.com/mcp).
Specify your Client ID and Client Secret under Advanced settings.
Click Add.
Kiro CLI — token headers
Sign in at https://developer.amazon.com/ and copy your application's clientId from the Login with Amazon console, and complete an authorization grant to get an access token. Then add this to ~/.kiro/settings/mcp.json with your clientId and access token in the Amazon-Ads-ClientId and Authorization headers, and start kiro-cli.
KIRO CLI — TOKEN HEADERS · JSON
{
"mcpServers": {
"amzn-ads-mcp": {
"url": "https://advertising-ai.amazon.com/mcp",
"headers": {
"Authorization": "Bearer Atza|<YOUR_ACCESS_TOKEN>",
"Amazon-Ads-ClientId": "<YOUR_AMAZON_ADS_CLIENT_ID>",
"Accept": "application/json, text/event-stream"
},
"timeout": 60000,
"disabled": false
}
}
}
