Connects Claude to the Amazon Advertising API for managing sponsored product campaigns. You get tools to list profiles and campaigns, pull performance metrics like impressions and sales, update keyword bids, and create new campaigns. Includes a helper script to walk through the OAuth flow and grab your refresh token. The reporting implementation is simplified, so you'll want to extend it with the full async report polling if you need production grade analytics. Supports all three Amazon regions (NA, EU, FE) and covers Sponsored Products comprehensively, with partial support for Sponsored Brands and Display. Reach for this when you're optimizing ad spend or need to automate campaign adjustments based on performance data.
A Model Context Protocol (MCP) server that provides tools for interacting with the Amazon Advertising API. This server enables AI assistants to access and manage Amazon Ads campaigns, keywords, performance data, and more.
This MCP server provides the following tools:
We provide a helper script to obtain your refresh token through the OAuth flow:
Create a .env file in the project root:
AMAZON_ADS_CLIENT_ID=your_client_id_here
AMAZON_ADS_CLIENT_SECRET=your_client_secret_here
Run the OAuth helper script:
npm run get-token
Your browser will open to Amazon's authorization page
Sign in and authorize the application
The script will display your refresh token - copy it to your .env file
Determine your advertising region:
git clone <your-repo-url>
cd amazonads-mcp
npm install
npm run build
Create a .env file or set the following environment variables:
AMAZON_ADS_CLIENT_ID=your_client_id
AMAZON_ADS_CLIENT_SECRET=your_client_secret
AMAZON_ADS_REFRESH_TOKEN=your_refresh_token
AMAZON_ADS_REGION=NA # Options: NA, EU, FE
AMAZON_ADS_SANDBOX=false # Set to true for testing with sandbox API
Add this server to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"amazonads": {
"command": "node",
"args": ["/absolute/path/to/amazonads-mcp/build/index.js"],
"env": {
"AMAZON_ADS_CLIENT_ID": "your_client_id",
"AMAZON_ADS_CLIENT_SECRET": "your_client_secret",
"AMAZON_ADS_REFRESH_TOKEN": "your_refresh_token",
"AMAZON_ADS_REGION": "NA"
}
}
}
}
Once configured in Claude Desktop, you can ask Claude to:
amazonads-mcp/
├── src/
│ ├── index.ts # Main MCP server implementation
│ └── amazon-ads-client.ts # Amazon Ads API client
├── build/ # Compiled JavaScript output
├── package.json
├── tsconfig.json
└── README.md
npm run build
Watch for changes and rebuild automatically:
npm run watch
Run the server directly:
npm start
The server communicates over stdio and expects MCP protocol messages.
This server currently supports:
Rate Limiting: The Amazon Ads API has rate limits. The client does not currently implement rate limiting logic.
Reporting API: The get_campaign_performance tool uses a simplified implementation. For production use, you should implement the full async reporting flow:
Error Handling: API errors are returned to the caller. Ensure proper credential configuration to avoid authentication errors.
Regions: Make sure to set the correct region (NA, EU, FE) based on your Amazon Ads account.
.env file or expose API credentialsMIT
Contributions are welcome! Please feel free to submit a Pull Request.
AMAZON_ADS_CLIENT_ID*Amazon Ads API Client ID
AMAZON_ADS_CLIENT_SECRET*secretAmazon Ads API Client Secret
AMAZON_ADS_REFRESH_TOKEN*secretAmazon Ads API Refresh Token
AMAZON_ADS_REGIONAmazon Ads region (NA, EU, or FE)
io.github.shelvick/shopify-subscription-reconciliation
zleventer/google-ads-mcp
csoai-org/meok-stripe-acp-checkout-mcp
io.github.mharnett/google-ads
csoai-org/stripe-billing-mcp
co.pipeboard/google-ads-mcp