โ Back to Blogs
Amazon Ads
11 min read
Amazon's Official Ads MCP Server: What It Does and Who It's For

Onieque Edwards
Content Strategist /Blog Writer

Picture a seller who reads that Amazon now lets Claude work on your ads. She opens Claude, looks for an Amazon Ads button, and finds nothing she can click. So she assumes she misread it.
She did not. She has just met the gap between what the headline says and who the product is built for.
The Amazon Ads MCP server is Amazon's own connector between AI assistants and its advertising system, and the Amazon Ads API is the doorway it sits on. An API is the route one piece of software uses to talk to another. MCP, short for Model Context Protocol, is a shared standard that lets an assistant like Claude use those routes as tools. Put together, the server lets an assistant read and change an ad account. Who gets to plug it in is the part most coverage skips.
In this article
What Is the Amazon Ads MCP Server?
Is the Amazon Ads MCP Server in Open Beta or Closed Beta?
What Can the Amazon Ads MCP Server Do?
Who Can Use the Amazon Ads MCP Server?
Is the Selling Partner Plugin for Claude the Same Thing?
Is It Safe to Let an Assistant Delete Campaigns?
Can a Seller Connect to the Amazon Ads MCP Server Directly?
Should You Use It Directly, Through a Provider, or Wait?
FAQ
What Is the Amazon Ads MCP Server?
It is an official Amazon product that connects AI agents to Amazon Ads API functionality. Those are Amazon's words. An agent here simply means an assistant that can take steps, as well as answer questions.
Before it existed, you had to build your own connection to the Ads API, or use a third-party tool that had. The timeline is short, and it matters because older articles are now out of date:
13 November 2025. Amazon opened a closed beta. Partners could request access through Amazon's developer portal, according to PPC Land's coverage at the time.
2 February 2026. Amazon announced an open beta, presented by Paula Despins, VP of Ads Measurement. Amazon's page describes it as "available globally in open beta to Amazon Ads partners with active API credentials".
30 September 2026. Amazon added a new tier on the same server called expert tools. The first is an AMC SQL Generator, which turns a plain-English question into a query for Amazon Marketing Cloud, Amazon's data workspace for advertisers. It is in closed beta, US only.

Amazon names Claude, ChatGPT and Gemini as assistants that can connect in the open beta. Any 2025 article saying there is no official Amazon MCP server is now wrong.
Is the Amazon Ads MCP Server in Open Beta or Closed Beta?
The honest answer is that the sources disagree, and I could not settle it.
Amazon's announcement page says open beta, dated 2 February 2026. PPC Land, which has covered the server closely, reports that Amazon's technical documentation still lists it as a closed beta. The documentation page itself would not load beyond its title when I tried to read it, so I cannot tell you which is current.
You may also see February 2025 or March 2026 given as launch dates. Amazon's own page says 2 February 2026, so use that.
Before you plan around it, check the current status on Amazon's Ads API documentation. And do not read "open beta" as "anyone can sign up today". It does not mean that, for reasons covered below.
What Can the Amazon Ads MCP Server Do?
According to Amazon's open-beta announcement, the server exposes tools for:
creating, updating and deleting campaigns
running performance and reporting queries
reading and changing account-level settings
reading billing and financial data
Amazon also added pre-built workflow tools for common jobs, such as creating accounts, generating reports, launching campaigns and expanding into new countries. Its two worked examples are expanding campaigns to another country in a single prompt, and building a full Sponsored Products campaign, with its ad groups and ads, "ready for review and approval".
PPC Land reports the tools sit in four groups: account management, billing, campaign management and reporting. Its closed-beta article also says a connecting app could filter tools to read-only ones. The open-beta coverage does not repeat that, so treat it as reported, not confirmed.
Amazon adds its own caution: connectivity "alone doesn't guarantee reliable outcomes". A connection hands over the controls, not the judgement.
Some things are not documented anywhere I could read. Amazon publishes no price for the core server, so I cannot tell you it is free or paid. The expert tools are the exception: beta costs are covered, and at general availability, planned for early 2027, they move to pay-per-use through AWS Marketplace. Rate limits, meaning how many requests you can send in a period, are not stated. Nor is any audit log for the server itself.
Who Can Use the Amazon Ads MCP Server?
Amazon says the server is for "advertisers and partners" who want a single integration for their own agents or AI platforms. The gate is in the phrase "active API credentials".
Ads API credentials are the approved keys that let software act on an ad account. Getting them means applying for Amazon Ads API access and setting up a Login with Amazon app, which is Amazon's sign-in system for third-party software, according to the third-party setup guides. Intentwise, which sells its own Amazon data connector, notes that "some programming knowledge is needed".
So the server is not a click-and-connect product for a seller who has never touched the Ads API. In practice it suits companies that already hold approved Ads API access, whether they build advertising software or run an agency, and larger brands with a developer in-house.
Most individual sellers will reach it, if at all, through a tool or an agency that sits on the Ads API, not by connecting their own assistant to it.
Is the Selling Partner Plugin for Claude the Same Thing?
No, and the two get mixed up often.
On 23 September 2026, at Amazon Accelerate, Amazon announced a Selling Partner plugin for Claude and Amazon Quick. It is a separate, seller-facing product, and it works on the Seller Central side of the business: listings, performance metrics, inventory levels and sales analytics.
The differences that matter:
It covers Seller Central data, not advertising. Amazon's page does not list Ads as one of the plugin's integrations.
It is built for sellers to connect themselves. Amazon describes the Claude connection as taking "roughly 60 seconds, no coding". It is in beta in Claude, for US stores only.
It has approval and a log built in. Amazon says actions need seller review and approval, every action is recorded in an audit trail, and the seller can choose recommend-only mode.
Amazon does not call it an MCP server. Its announcement page never mentions MCP. Some vendors label it that way, but Amazon does not, so I will not either.
If your question is about stock, listings or sales, the plugin is the closer fit. If your question is about campaigns, bids and ad reports, it is the Ads MCP server, or a tool built on the Ads API.
Is It Safe to Let an Assistant Delete Campaigns?
"Delete" is on Amazon's own list of what the server can do. That is the line to read twice.
With write access, a live account can change in seconds. Adbrew, which builds its own ad software, points out that changes apply immediately and that the server carries out requests without judging whether the strategy is sound. An ads-only connection also has no view of stock levels, margin, Buy Box ownership or organic rank. Adbrew's example is a bid raised on a product about to run out of stock. The example is theirs, but the scope point matches Amazon's own description of the server.
I found no reported case of an Amazon MCP server changing bids or budgets by mistake, and I am not suggesting one has happened. The point is that some changes cannot be undone. Seller Labs notes, for its own tool, that a removed negative keyword cannot be restored.
This is why write access needs approval steps. Amazon's own campaign example stops at "ready for review and approval", and its Selling Partner plugin requires seller sign-off on every action. Any setup on the ads side should hold the same line. Start read-only, and switch write access on deliberately, with a person approving every change that touches spend or deletes something. Then keep a record of what changed and who approved it.
And never paste a Seller Central password into any connector's settings file, which is Seller Labs' advice and good advice.
Can a Seller Connect to the Amazon Ads MCP Server Directly?
Here is a worked example of how one seller would work out which route applies. It is illustrative, not taken from an account.
Maria runs a US brand on Amazon. She manages Sponsored Products herself in the ads console. She has no developer and has never applied for Ads API access. She uses Claude for writing and wants it to help with her ads.
She works through three questions.
First, does she hold active Amazon Ads API credentials? No. That rules out connecting her own assistant to the official server today. Getting there means applying for API access and setting up a Login with Amazon app, which is a developer job.
Second, is her question about ads, or about the rest of the store? Mostly ads. She wants to know which campaigns are spending without selling. The Selling Partner plugin would not answer that, since Amazon does not list Ads among its integrations. If her question had been about inventory or listings, the plugin would have been the obvious place to start.
Third, does she need the assistant to change anything, or only to read? For now, only to read. She wants a second pair of eyes on the reports before she touches a bid.
Her answer is a provider already approved on the Ads API, ideally one that is read-only by default. She gets the ads data into her assistant without becoming a developer, and nothing changes without her say.
Compare an agency that already holds an approved Ads API application and has someone to configure it. For them the official server is a direct option, once they settle the beta status and put approval steps in front of every write.

If you want the questions to put to a provider before you hand over access, I have written them up in a separate article, Questions to Ask an Amazon MCP Provider Before You Sign Up.
Should You Use It Directly, Through a Provider, or Wait?
The decision comes down to two things you already know about your business: whether you hold Ads API access, and how much of your ad budget you are willing to let software touch without a person in the loop.
Use it directly if you already hold active Ads API credentials, have someone who can configure it, and will put approval steps in front of every write. You get Amazon's own connection and skip the middle layer. You also carry the beta risk and own every change.
Use it through a provider if you have no API access and want ad data in your assistant now. You are paying for the API approval and the safety controls you would otherwise build yourself. Choose on what the provider documents in writing: whether it starts read-only, and whether every change waits for your approval and gets logged.
Wait if your current reporting already answers your questions, or if write access would touch an account you cannot afford to have changed without review. The status is contested, no price is published and rate limits are undocumented. That is no reason to avoid it for good. It is a reason not to move budget-touching work onto it yet.
Whichever route you take, the server only sees the ad account. Cutting spend on a product about to stock out still needs someone reading ads against inventory, price and rank. That does not come with the connection.
So the question to answer before anything else is this: which of your ad decisions are you comfortable letting software make without a person signing off?
Not sure which route fits your account?
If you are weighing whether an assistant should touch your Amazon ads at all, and which parts of the account it should never touch without you, that is a good first conversation. The Expedition Audit reads your ads against your stock, pricing and rank, so you can see where an automated change would help and where it would cost you. Book it here.
FAQ
Is there an official Amazon MCP server?
Yes. Amazon's Ads MCP server connects AI assistants to the Amazon Ads API. It entered closed beta on 13 November 2025, and Amazon announced an open beta on 2 February 2026.
Is the Amazon Ads MCP server in open beta?
Amazon's announcement says open beta. PPC Land reports that Amazon's technical documentation still lists it as closed beta. Check the current status before you plan around it.
What can the Amazon Ads MCP server do?
Amazon says it can create, update and delete campaigns, run performance and reporting queries, manage account-level settings and read billing data. It also has pre-built workflow tools for jobs such as launching campaigns and expanding to new countries.
Can I connect Claude to my Amazon ads without API access?
Not to the official server directly. It needs active Amazon Ads API credentials. Without them, the practical route is a tool or agency that already holds Ads API access.
Is the Amazon Selling Partner plugin for Claude an MCP server?
Amazon does not describe it as one. It is a separate product announced on 23 September 2026 that brings Seller Central data such as listings, inventory and sales into Claude and Amazon Quick. Amazon does not list advertising among its integrations.
How much does the Amazon Ads MCP server cost?
Amazon's announcement states no price for the core server. The newer expert tools are free during beta and are planned to move to pay-per-use through AWS Marketplace at general availability in early 2027.
Sources
Amazon's own announcement, Introducing the Amazon Ads MCP Server (2 February 2026), is the source for the open-beta date, the "open beta to Amazon Ads partners with active API credentials" wording, the list of tools, the workflow examples, the named assistants, the "advertisers and partners" audience and the caution that connectivity alone does not guarantee reliable outcomes. Amazon's Ads MCP documentation page loaded as a title only when read on 9 November 2026. PPC Land's coverage of the closed beta (13 November 2025) gives the closed-beta date, the four tool groups and the read-only filtering, and its open-beta article (2 February 2026) reports that the technical docs still list closed beta. Amazon's expert tools announcement (30 September 2026) covers the AMC SQL Generator, its closed beta and the planned pay-per-use pricing. Amazon's page on the Seller Assistant and Selling Partner plugin covers the plugin's data, approval, audit trail, recommend-only mode and setup time, and The Next Web dates the announcement to 23 September 2026. Intentwise's explainer on the Amazon MCP (9 February 2026) is the source for "some programming knowledge is needed". Adbrew's article on the Amazon Ads MCP is the source for changes applying immediately and the near-stockout example. Seller Labs' guides on using MCP with seller tools (29 July 2026) and its MCP FAQ (21 October 2026) are the sources for the password advice and the negative keyword that cannot be restored.

Onieque Edwards
Content Strategist /Blog Writer
Onieque is the brain behind bold Amazon growth strategies and structured business execution. He enjoys turning scattered ideas into clear, actionable systems that actually drive results. When heโs not building out growth plans or refining campaigns, youโll likely find him exploring new coffee spots or getting lost in ideas that connect strategy with creativity.
