A managed MCP server for Amazon Seller Central and Amazon Ads

What the connection gives your AI tool

• List the Amazon accounts and tools a connection is allowed to use.
• Read Sponsored Products campaigns, ad groups and keywords live from Amazon Ads.
• Request and download Amazon Ads campaign, keyword, search-term and advertised-product reports.
• Read catalog items, listings, order metrics, inventory and financial events live from the Selling Partner API.
• Update keyword bids, daily campaign budgets and campaign state, each with explicit confirmation.
• Call other Amazon Ads or Selling Partner API endpoints the connected application can reach: GET requests with a read scope, and other methods with a write scope and explicit confirmation.
• On Data plans, query retained campaign, ad, product, revenue, cost and fee history with source and coverage details.

The full list of tools, with the scope each one needs, is in supported Amazon data and tools.

How it works

1. Connect Amazon to a workspace

   Create an Agentic Sellar workspace and authorize Seller Central (Selling Partner API) and Amazon Ads with Amazon’s own consent screens. Amazon issues the credentials to Agentic Sellar, where they stay.

2. Add the MCP URL to your AI tool

   Paste https://agenticsellar.com/mcp into your client as a remote MCP server or custom connector. There is no API key to copy and no LLM key to share.

3. Sign in and choose accounts

   Your AI tool opens an Agentic Sellar sign-in. A workspace owner picks the Amazon accounts the connection may use, and the consent screen says whether the tool is asking for write access.

4. Ask in plain language

   Ask for campaign performance, search-term reports, inventory or fee records. Write tools need an explicit confirmation argument and are labelled as destructive actions, so clients such as Claude and ChatGPT can ask you to approve a bid, budget or listing change before Agentic Sellar calls Amazon.

Step-by-step instructions: getting started.

Seller Central and Amazon Ads coverage

Seller Central and Amazon Ads accounts in Amazon’s North America, Europe and Far East regions. One Amazon sign-in per region covers that region’s marketplaces and advertising profiles.

Supported AI clients

Read and write access

Reads and writes are separate OAuth scopes for each Amazon API. A new connection asks for the read scopes, and holds only the scopes a workspace owner approved.

How grants, scopes and confirmation work in detail: permissions and scopes.

OAuth, approvals and audit

• AI clients sign in with OAuth 2.1 authorization code flow and PKCE (S256). No API key or LLM key is pasted into the AI tool.
• Amazon refresh tokens stay on Agentic Sellar’s servers, encrypted at rest with AES-256-GCM. AI clients receive their own short-lived credentials and never see Amazon credentials.
• Access tokens expire after 60 minutes. Refresh tokens rotate on every use, and reusing an old one revokes the whole grant.
• Authorization codes, access tokens and refresh tokens are stored only as hashes.
• A connection lasts at most 30 days and can be revoked at any time from the Agent access page.
• Only workspace owners can authorize a new AI connection. They choose which Amazon accounts it can use and which scopes it gets: the consent screen lists every scope with the AI tool’s request ticked, and the owner can untick write scopes to approve read-only access.
• New connections are asked for read scopes only. A write scope is granted only when a workspace owner ticks it on the consent screen, when connecting or when the AI tool calls a write tool and asks for more access.
• Write tools require a write scope and an explicit confirm=true argument on every call, and are labelled as destructive MCP actions so clients such as Claude and ChatGPT can ask you to approve each one. Campaign archiving is excluded from the curated write tools because it cannot be undone.
• Tool calls that reach Amazon accounts are limited to 120 a minute per workspace, shared by its AI connections, on top of plan concurrency and monthly work-unit limits.
• Every tool call that passes access checks leaves a receipt recording the operation, account, status and time. Receipts do not store report contents or tokens.

Read the full agent access security model or our security and disclosure policy.

How this relates to Amazon’s own AI tools

Amazon opened its Amazon Ads MCP Server as an open beta in February 2026 for the Amazon Ads API. Amazon’s Selling Partner plugin brings Seller Assistant into Amazon Quick and, in beta, Claude for sellers in Amazon’s US stores. Agentic Sellar is an independent, managed connection: Amazon Ads and Seller Central behind one OAuth sign-in, usable from any OAuth-capable MCP client, with account-level grants, confirmed writes and call receipts. Some teams will use more than one of these. We compare them in detail in Amazon Ads MCP Server alternative: when you also need Seller Central.

Pricing

The Access plan is $59 a month for live Amazon reads and updates over MCP and REST, with unlimited connected Amazon accounts. Data plans start at $149 a month and add retained history for the products you choose. Compare plans.

Limitations

• Whether an AI tool asks for more access by itself when it reaches a write tool depends on the client. If yours does not, reconnect it: for an hour after the refused call, the consent screen ticks the scope that tool needed for you to approve, and you can always tick it yourself.
• Agentic Sellar does not choose bids or budgets on its own. Changes come from your AI tool; how it asks for approval before a write depends on the client and your settings there.
• Live reads return what Amazon’s APIs return at request time. Amazon’s own report delays and attribution windows still apply.
• Retained history starts when a Data plan begins collecting it, plus the history Amazon makes available (about 93 days for advertising reports).
• Agentic Sellar is independent and is not affiliated with or endorsed by Amazon, Anthropic or OpenAI.

Frequently asked questions