Amazon Ads MCP in Kiro
Amazon exposes a Model Context Protocol (MCP) server for Amazon Advertising AI, which tools like Kiro can use to call advertising capabilities with your credentials. This page summarizes how to point Kiro at the MCP endpoint and which headers and IDs you need. It mirrors Amazon’s public guidance; always refer to the latest docs in the Amazon Ads API documentation for authoritative details.
MCP server URL
Use this as the MCP endpoint in your client:
https://advertising-ai.amazon.com/mcp
Prerequisites
- Login with Amazon (LWA) application (
Amazon-Ads-ClientIdis your LWA client identifier). - Appropriate Amazon Ads API access for your advertiser profile.
- A short-lived access token in the form
Atza|…(obtain via LWA token exchange; refresh tokens belong only in secure storage, never in docs or repos). - Your Amazon Advertising profile ID when you need to scope requests to a single profile.
If a refresh token or access token was ever pasted into chat, email, or a public repo, treat it as compromised and rotate it in the LWA console.
HTTP headers
Typical headers sent with MCP requests:
Authorization: Bearer Atza|<access_token>Amazon-Ads-ClientId: <your LWA client id>- Optional:
Amazon-Advertising-API-Scope: <profile_id>to pin a profile. - Optional:
Amazon-Ads-AI-Account-Selection-Mode: FIXEDwhen using a fixed profile scope (per Amazon’s MCP guidance).
Kiro settings file
On many setups, Kiro reads MCP configuration from a JSON file in your user settings directory:
- Windows:
%USERPROFILE%\.kiro\settings\mcp.json - macOS / Linux:
~/.kiro/settings/mcp.json
Replace placeholders with your own values. Do not commit real tokens.
{
"mcpServers": {
"amazon-advertising-ai": {
"url": "https://advertising-ai.amazon.com/mcp",
"headers": {
"Authorization": "Bearer Atza|YOUR_ACCESS_TOKEN",
"Amazon-Ads-ClientId": "YOUR_LWA_CLIENT_ID",
"Amazon-Advertising-API-Scope": "YOUR_PROFILE_ID",
"Amazon-Ads-AI-Account-Selection-Mode": "FIXED"
}
}
}
}
Exact JSON shape may vary by Kiro version; align field names with what your editor expects for “remote MCP” or “HTTP” servers.
Related
For Partner Network API onboarding and LWA linking, see API Access. For this site’s OAuth connection (separate from MCP file editing), use Connect Amazon Ads in the header.