Agent Central vs Amazon’s first-party ads server.

Amazon Ads MCP Server is a first-party server for advertising data, hosted at advertising-ai.amazon.com. It has been in open beta since February 2026 and covers Sponsored Products, Sponsored Brands, Sponsored Display, DSP, AMC, and account management. Amazon does not publish a stable tool count. It is free and provides first-party Ads API access.

The name is the tell. It is an Ads server. It does not touch inventory levels, FBA shipments, orders, returns, catalog health, listing quality, keyword rank tracking, financial events, or Multi-Channel Fulfillment. If a workflow needs to compare days of cover with budget data, or review settlement economics after a pricing change, the Amazon Ads server does not include those non-advertising domains. The agent would need a second data source for every domain outside advertising.

Agent Central covers all six. 177 tools across ads, inventory, orders, catalog, finance, and fulfillment sit behind a single bearer token. The agent does not switch between servers or stitch together disconnected API responses. One connection, every domain an operator asks about day to day.

The second difference is the data architecture. Amazon’s server uses live API calls for current Ads operations, while report-based reads remain asynchronous. Completion time varies by operation, so an agent issuing several report-backed follow-ups may need to wait between results.

Agent Central inverts the data path. We sync your seller data into account-isolated storage on a cadence we control. Amazon source lag still applies: Business Reports are typically 48 to 72 hours behind, ad metrics continue settling for 48 to 72 hours, and orders refresh more frequently. When your agent calls a tool, the response comes back in under a second from prepared seller data, so follow-ups stay cheap and the agent can iterate. For tasks that require current Amazon source fields, Agent Central also has 20 direct API tools that call Amazon live.

Pre-synced data also enables joins the API surface keeps separate: TACOS calculated from ads spend and total sales, keyword rank stitched to search volume and SERP share, days of cover with FBA stock and inbound shipments and recent velocity in the same row. An ads-only server cannot compute cross-domain metrics because it does not have the other domains.

Both servers support write operations. Amazon’s server provides campaign CRUD and bid/budget updates, but without a documented preview/confirm flow, audit trail, or hard limits. If an agent updates the wrong bid, you find out from a performance report.

Agent Central wraps every write tool in guardrails. Changes preview by default before applying. Before a bid update the tool reads the current bid; before a quantity update it reads the current stock; before a price change it reads the current price and the competitive landscape. Hard limits prevent the agent from cutting a $2 bid to a single cent or jumping a $20 price to $200. Every mutation carries an idempotency key and lands in an audit log with the previous value, the new value, the API key that made the call, and the timestamp. You can scope a key to read-only when you want the agent to analyze without the ability to act.

Data history is the last gap. Amazon’s available history varies by report and API surface. Paid plans can import up to 730 days of history, depending on what Amazon makes available. Recent data comes first; older history follows.Year-over-year comparisons work when both requested windows are available in the account.

If you already use Amazon’s Ads MCP Server and want to keep it, that is fine; the two are not exclusive. Amazon’s server is strong for first-party live Ads API operations. Agent Central handles broader analytical work where cross-domain context, bounded history, prepared-read speed, and write safety matter.