How to Connect the Amazon Ads MCP Server to Claude

This guide connects Amazon’s official Amazon Ads MCP Server, the first-party server that reached open beta in February 2026, to Claude. Claude was one of the first clients to support the Model Context Protocol, so the process is quick once your API access is in place.

What you need first

Get these in place before you touch any config:

• Claude Desktop or Claude Code installed.
• An Amazon advertiser, Seller, or Vendor account with active campaigns. Amazon will not approve API access for an account with no ad spend.
• Amazon Ads API access for your account, set up with the steps below. A managed third-party server skips this, since the provider already holds the access.

Getting Amazon Ads API access (the real prerequisite)

This is the part that takes the longest, mostly the approval wait, so do it first.

1. Go to the Amazon Developer portal and sign in with the exact email tied to your Seller or Vendor account, then complete developer registration.
2. Open the Amazon Ads API onboarding guide and click Request Access. Choose “I want to manage my own advertising,” add your company name, and select the markets you advertise in.
3. Wait for approval, typically one to three business days. If you are rejected, the usual cause is no active ad spend, so make sure campaigns are running and reapply.
4. Create a Login with Amazon (LWA) security profile, then copy its Client ID (begins amzn1.application-oa2-client.) and Client Secret (begins amzn1.oa2-cs.v1.), and set an allowed return URL that matches what your server expects.
5. Link that security profile to your Amazon Ads API application in the Ads console, not the developer portal. Skipping this is the top reason authorization fails later.

The fuller version, with the full credentials breakdown, is in how to set up Amazon Ads MCP.

Two things from Amazon’s connection docs are worth knowing before you connect:

• Your region. The official server has a regional endpoint for North America, Europe, and the Far East. Use the one that matches your account.
• Your account context. You connect either as a single account (you set one profile) or a manager account (agencies reaching many client accounts under one application).

The five steps

1. 1
   Add the server URL to Claude Point Claude at the official Amazon Ads MCP Server endpoint. No install.
2. 2
   Reopen Claude Fully quit and relaunch so it loads the new server.
3. 3
   Run the OAuth flow Ask Claude to start it, approve with your Amazon account, then confirm.
4. 4
   Set an active profile Tell Claude which account and marketplace to manage.
5. 5
   Validate Run a read-only prompt and check the numbers before any writes.

Step 1: Add the server to Claude

You connect to the official server with a small JSON block that points at its URL. The server is not region agnostic, so use the endpoint that matches your account’s region:

Region	Endpoint URL
NA (North America)	https://advertising-ai.amazon.com/mcp
EU (Europe)	https://advertising-ai-eu.amazon.com/mcp
FE (Far East)	https://advertising-ai-fe.amazon.com/mcp

The examples below use the NA URL. Swap in your region’s URL if you are not in North America.

Claude Desktop reads claude_desktop_config.json (at ~/Library/Application Support/Claude/ on macOS, or %APPDATA%/Claude/ on Windows):

{
  "mcpServers": {
    "amazon-ads": {
      "type": "streamable-http",
      "url": "https://advertising-ai.amazon.com/mcp"
    }
  }
}

Claude Code can do the same two ways. Either add the block to ~/.claude/mcp.json, or run one command in your terminal:

claude mcp add --transport http amazon-ads https://advertising-ai.amazon.com/mcp

Because the official server uses OAuth, you do not paste any key here. If a server uses a bearer token instead, add it as a header: "headers": { "Authorization": "Bearer YOUR_TOKEN" }.

Step 2: Reopen Claude

Fully quit and relaunch Claude so it loads the change. You should now see amazon-ads listed as an available tool or connector.

Step 3: Run the OAuth flow

The server is connected, but it cannot touch your account until you authorize it. Type each prompt and watch what comes back:

• “Start the OAuth flow for Amazon Ads.” Claude returns a unique authorization URL.
• Open that URL, sign in with your Amazon account, and click Allow. You should see an “authorization successful” page.
• “Check the OAuth status.” Claude should reply that you are authenticated.

Step 4: Set an active profile

Amazon Ads works in profiles, where each profile is one account in one marketplace.

• “List my Amazon Ads profiles.” Claude returns each profile’s ID, type, and account name.
• “Set the active profile to [your profile ID].” This is required before any reporting or campaign tool will run.

If you connect as a manager account (common for agencies), you set the client account you want to act on the same way, choosing from the accounts your application can reach.

Step 5: Validate before you trust it

Start with read-only prompts and confirm the numbers against the Amazon Ads console:

• “List my Sponsored Products campaigns.”
• “Show my top keywords by spend over the last 30 days.”

If those return accurate data, the connection works. Only then try a small, low-risk write and confirm it behaves before doing anything at scale. For ideas, see Amazon Ads MCP use cases.

Troubleshooting

• “Invalid redirect URI” in the browser. The callback URL in your Login with Amazon profile does not match what the server expects. Make them identical.
• Browser says success, but Claude says not authenticated. Your LWA security profile is not linked to your Amazon Ads API application. Link it in the Ads console, then re-run the status check.
• amazon-ads does not appear in Claude. Recheck the JSON for typos, confirm the file path, and fully restart Claude.

Related reading

• About the server itself: the official Amazon Ads MCP Server
• The full setup picture: how to set up Amazon Ads MCP
• Using a different client: connect Amazon Ads MCP to ChatGPT

Sources

1. Amazon Ads, “Introducing the Amazon Ads MCP Server” (open beta, connecting clients). advertising.amazon.com
2. Amazon Ads, “Amazon Ads API authorization overview” (Login with Amazon, profiles). advertising.amazon.com