How to choose an Amazon Ads MCP: 6 questions to ask first

What should you ask before you choose an MCP for Amazon ads?

Ask six questions, in this order, and get each answer in writing. A demo shows you the best prompt. A checklist shows you what the connection allows on a live account.

Xnurta MCP connects Claude, ChatGPT and other MCP clients to your Xnurta data, and the answers below describe it. The questions work on any MCP, including ours, so run them on every option you shortlist.

Who can connect, and with whose login?

The strong answer is that each person signs in as themselves and sees only what their own login already carries. The weak answer is one shared credential that the whole team pastes into their tools.

Amazon says its Amazon Ads MCP server is available to Amazon Ads partners with active API credentials. That is a different starting point from a personal login, so ask any provider which one you need.

On Xnurta MCP, OAuth sends you through a browser sign-in with your own Xnurta login. You see only the ad accounts and permissions that login carries, main and sub-accounts included. On Claude Team or Enterprise, an Owner adds the connector once and each member then connects individually. Adding it at the organization level does not widen anyone's access.

The other route is an MCP token. You create it in Xnurta under MCP & Skill, choose New token and pick the scope. Copy it right away, because it cannot be viewed again. Claude desktop, Cowork and claude.ai have no field for a token, so they use OAuth. The endpoint is https://mcp.xnurta.com/mcp.

What can it read, and how far back?

Ask for the list: which data, how far back, how fine the granularity and how fresh. If the answer is "everything, in real time," keep asking.

Xnurta MCP has three query tools, for ads performance, entity metadata and the operation log. Queries are read only, so asking never changes your account. History runs about 15 months across 22 marketplaces. Data is daily by default, with hourly data for SP, SB and SD campaigns and SP keywords. Campaign performance can also be broken out by audience.

Freshness follows the Xnurta platform's update cadence. It is not real time, and a good provider says so.

What can it change, and how are the changes separated?

Ask for the writes as a list, and ask which permission each one needs. The strong answer names the kinds of write and gives each its own permission, so access to one does not quietly include another.

Xnurta MCP has three kinds of write, each with its own permission scope:

1. Managed group management: create, edit, schedule and delete AI managed groups, one at a time or in bulk.
2. Ad-entity editing: campaign state, budget and bidding strategy, products, negatives, placement and audience bid adjustments, and keyword and product targets with their state and bid.
3. Sponsored Products campaign creation: campaigns with ad groups, products, targeting, negatives, placement bid adjustments and an optional AMC audience, created in one atomic request. If any campaign in the request fails validation, none are created.

A scope that edits ads does not necessarily create campaigns. Campaigns cannot be deleted. They can only be archived, and archiving is irreversible, so create campaigns paused if you want to review them before they spend. Deleting a managed group archives it, which is also irreversible.

What do you see before it changes money?

Ask what the preview shows and when it appears. A strong answer is a preview of the exact objects with old value and new value, and nothing submitted until you confirm.

On Xnurta MCP, anything involving money, bids or archiving returns a preview first. It shows which objects will change and from what value to what value. The assistant submits only after you confirm. For managed group changes and campaign creation, ask the assistant to show the full configuration or structure before it submits.

Amazon describes one review step for its Sponsored Products campaign tool: the output only needs review and approval. For anything beyond that, read Amazon's documentation. Do not assume.

Where do you see what happened afterwards?

Ask what the change log records and how you can filter it. The strong answer is a log you can query in plain language by who, what, where and when.

The Xnurta operation log holds human and AI actions on campaigns, ad groups, targets, bids, budgets and managed groups. You can filter by operator (the AI, a human, an automation rule or one person's email), by action type, by entity type and by the Amazon entity ID. Reading it is read only. Who changed my Amazon campaign? walks through the prompts.

Does it work in the assistant your team already uses?

Check the clients, the setup and whether the team can repeat good work. Setup that needs a developer is a weak answer for most ad teams.

Xnurta MCP works with Claude, Claude Code, ChatGPT Codex, Cherry Studio, WorkBuddy and other MCP clients. Claude desktop, Cowork and claude.ai connect through a custom connector. Claude Code and ChatGPT Codex take one prompt that points at the Xnurta MCP repository on GitHub. Connect Claude or ChatGPT to Xnurta MCP gives the exact screens.

Adding a connector never installs skills, so ask the assistant to install them from the repository in a new chat. Skills teach the assistant the routine for a task. Official ones include Weekly Ads Report, Search Term Traffic Diagnosis, Amazon Ads Operation Log Query and Amazon SA Campaign Creation. Your team can also build its own and keep it private or share it with your organization.

How do you test an MCP for Amazon ads before you trust it?

Run the same short test on every option, on one real ad account, before anyone signs anything. Treat any speed or accuracy figure as unproven until you can repeat it yourself.

1. Connect with your own login, then ask the assistant which ad accounts it can see. Compare the list with what you expect.
2. Ask a read question you already know the answer to. Check the numbers against the Amazon console.
3. Ask who changed a campaign and compare the answer with what your team remembers.
4. If write access is on, create one paused campaign and read the preview before you confirm.
5. Find the change afterwards and note what the provider's log shows.

Call get_user_authorized_context and list the ad accounts I'm authorized to access.

In ad account [account name], rank campaigns by ACOS for the last [7] days compared with the prior week. Show spend, orders and ACOS in a table.

In ad account [account name], create a paused SP auto campaign for these [5] ASINs with a daily budget of [amount]. Show me the full structure before you submit it.

The write test needs write access, which your CSM turns on per account. To compare Xnurta MCP with Amazon's own server side by side, read Amazon's own Ads MCP server vs a platform MCP.