Installation guide

How to install Amazon Ads MCP Server

In Claude, ChatGPT, Gemini, Microsoft Copilot, Perplexity, Cursor and Claude Code, with what to check before you start and the first prompts to run.

The Amazon Ads MCP Server is hosted by Amazon Ads, so nothing runs locally. Connecting means adding the server to your AI platform or custom agent and authenticating with active Amazon Ads API credentials. The announcement does not give the server URL, the sign-in flow or client-specific steps. Take those exact values from the vendor's Amazon Ads MCP Server documentation, linked from the announcement page.

This should be done by someone at an advertiser or Amazon Ads partner who already holds Amazon Ads API credentials, such as an agency developer or the ad operations lead. The server is in open beta and exposes write tools that can change live spend. Start with an account or profile of limited scope, run read-only reporting first, and have a person approve every write action.

Amazon Ads MCP Server setup guide: Amazon Ads's MCP documentation page on advertising.amazon.com, shown in a browser frame (advertising MCP server for e-commerce) — Amazon Ads MCP Server setup guide preview: Amazon Ads’s documentation on advertising.amazon.com, captured Oct 13, 2026. The page may have changed since; the link opens the live version.

Before you start

Active Amazon Ads API credentials. The announcement says the open beta is available globally to Amazon Ads partners with these credentials.
The server address and authentication steps from the vendor's Amazon Ads MCP Server documentation, which is linked from the announcement page.
An AI platform or custom agent that supports remote MCP servers, such as Claude, ChatGPT or Gemini, as named in the announcement.
Access to the Amazon Ads console, so you can check reported numbers against it.
A limited-scope or test account or profile, where the documentation allows it, for first tests.

How it runs: Remote, added by URL
Access: Read and write
Server address: Copy it from the vendor documentation

Amazon Ads MCP Server in Claude

Open the vendor's Amazon Ads MCP Server documentation and copy the exact server URL and authentication requirements. The announcement does not list them.
In Claude.ai or the Claude Desktop app, open Settings > Connectors and choose to add a custom connector by URL.
Paste the server URL from the vendor documentation and give the connector a name such as Amazon Ads.
Complete authentication with your Amazon Ads API credentials, following the vendor documentation.
Start a new chat, enable the connector, and run a read-only reporting request first. The docs do not describe Claude-specific steps, so use Claude's standard custom connector flow.

Amazon Ads MCP Server in ChatGPT

Get the exact server URL and authentication method from the vendor's Amazon Ads MCP Server documentation. The announcement does not include them.
In ChatGPT, enable Developer mode in the connector settings. Availability depends on your plan and workspace admin settings.
Add a custom MCP connector and paste the server URL from the vendor documentation.
Authenticate with your Amazon Ads API credentials as the vendor documentation describes.
In a new chat, select the connector and ask for a read-only report. The docs do not cover ChatGPT-specific steps, so this is ChatGPT's standard custom connector flow.

Amazon Ads MCP Server in Gemini

Take the server URL and authentication details from the vendor's Amazon Ads MCP Server documentation. The announcement does not list them.
For Gemini CLI, open your settings JSON and add an entry under mcpServers with the remote server URL. Check the Gemini CLI documentation for the exact key name for remote servers.
Add any authentication headers or credentials the vendor documentation requires. Do not hard-code secrets in a shared file.
Restart Gemini CLI and confirm the server and its tools are listed.
Run a read-only reporting prompt first. The docs only name Gemini as a supported kind of platform and give no Gemini-specific steps.

Amazon Ads MCP Server in Microsoft Copilot

Get the server URL and authentication method from the vendor's Amazon Ads MCP Server documentation. The announcement does not cover Copilot.
For GitHub Copilot in VS Code, add a remote server entry to .vscode/mcp.json under servers, using the URL from the vendor documentation.
For Microsoft Copilot Studio, add an MCP tool or custom connector in your agent and supply the same URL and credentials.
Authenticate with your Amazon Ads API credentials as the vendor documentation describes.
Start with a read-only reporting prompt and check the figures against the Amazon Ads console.

Amazon Ads MCP Server in Perplexity

Take the server URL and authentication details from the vendor's Amazon Ads MCP Server documentation. The announcement does not mention Perplexity.
In the Perplexity desktop app, open the connectors settings and choose to add a custom remote MCP connector. Availability depends on your plan.
Paste the server URL and name the connector Amazon Ads.
Authenticate with your Amazon Ads API credentials as the vendor documentation describes.
Run a read-only reporting query first and compare the results with the Amazon Ads console.

Amazon Ads MCP Server in Cursor

Get the server URL and authentication requirements from the vendor's Amazon Ads MCP Server documentation. The announcement does not cover Cursor.
Open Cursor's MCP settings and choose to add a new MCP server, or edit the mcpServers JSON file.
Add an entry with the url value from the vendor documentation and any required headers or credentials.
Save the file and check that the server shows as connected with its tools listed.
Test with a read-only reporting prompt before enabling any write tools.

Amazon Ads MCP Server in Claude Code

Take the server URL and authentication requirements from the vendor's Amazon Ads MCP Server documentation. The announcement does not list them.
In a terminal, run claude mcp add --transport http amazon-ads <SERVER_URL>, replacing <SERVER_URL> with the URL from the vendor documentation.
Add any authentication headers or credentials that the vendor documentation requires. The docs do not describe Claude Code specifically.
Start claude and run /mcp to confirm the server is connected and to complete any sign-in.
Run a read-only reporting prompt first. Approve each write action manually.

Terminal

claude mcp add --transport http amazon-ads <SERVER_URL>

Check that it works

Start with questions that only read data. If these answer from your real account, the connection is good.

List the Amazon Ads profiles or advertiser accounts available to this connection. Do not change anything.
Run a read-only performance report for the last 7 days for one campaign and show the impressions, clicks, spend and sales. I will compare it with the Amazon Ads console.
List the tools this server exposes and mark which ones can create, update or delete campaigns.

Troubleshooting

+Why can't I connect or sign in to the server?

The open beta is aimed at Amazon Ads partners with active Amazon Ads API credentials. Confirm your credentials are active and cover the account or profile you are using. Then check the server URL and authentication steps against the vendor documentation, because the announcement does not list them.

+Why does my client not list the server or its tools?

Check that you used the exact server URL from the vendor documentation and that your client supports remote MCP servers on your plan. Restart the client or start a new session. Then confirm the connector is enabled for the chat or agent.

+Why do I get permission errors or empty reports?

The profile or account you authenticated with may lack access to the advertiser data you are asking about. Check the credentials' scope and ask for the specific profile. Compare the results with the Amazon Ads console. Do not widen access until read-only queries return correct data.

Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.