Amazon Ads MCP server for Claude.
agentcentral is a hosted Amazon Ads MCP server for Claude. After Amazon Ads OAuth and sync, Claude can call scoped MCP tools for campaigns, ad groups, keywords, search terms, placements, budget pacing, TACOS, Amazon Ads source-provided bid and budget suggestion fields, and optional guarded ads writes.
The Amazon Ads surface is part of the broader agentcentral seller data layer, so Claude can read ads facts alongside inventory, orders, catalog, ranking, and finance context when those domains are included in the key scope.
Last updated May 20, 2026.
- Claude fit
- Hosted Amazon Ads MCP server for Claude custom connectors and Claude Code
- Endpoint
- https://mcp.agentcentral.to/mcp
- Ads surface
- 38 Amazon Ads tools across reads, live Amazon fields, and guarded writes
- Metrics
- Spend, sales, ACOS, ROAS, CTR, CVR, TACOS, budget pacing, and placements
- Amazon source fields
- Bid and budget suggestion fields are labeled as Amazon-provided data
- Write access
- Optional per key, with pre-read checks and audit logs where supported
Hosted MCP endpoint
Header-capable MCP clients use https://mcp.agentcentral.to/mcp with an agentcentral bearer key.
Scoped access
API keys can be read-only, domain-scoped, or include supported write tools for a specific workflow.
Data-layer boundary
agentcentral returns source fields, normalized joins, deterministic metrics, classifications, and audit results.
Data coverage
What the MCP server exposes.
The hosted server is built around factual seller data that an AI client can query repeatedly. The client does the reasoning; the agentcentral tools provide the structured data surface.
Campaign and placement rows
Claude can query campaign, portfolio, ad group, keyword, product, purchased product, placement, Store, DSP, and attribution performance rows.
Search terms and keywords
Search terms, keyword performance, search query ad coverage, brand health, share of voice, and SQP joins are exposed through MCP tools.
Budget and bid fields
Budget pacing plus Amazon Ads API source-provided bid and budget suggestion fields are available with source attribution.
Seller-data joins
When scoped domains allow it, Claude can read ads data with inventory, orders, catalog, ranking, and finance fields through the same hosted MCP server.
Access model
How AI clients connect.
Connect Amazon once, let agentcentral sync the seller data, then give the AI client a scoped MCP credential or connector URL.
Connect Amazon Ads
Authorize Amazon Ads from the agentcentral dashboard so reporting data can sync into the account-isolated data layer.
Let ads data sync
agentcentral retains campaign snapshots, report rows, search terms, budget usage, and related ads history for repeated reads.
Create Claude access
Generate a signed Claude connector URL or a scoped bearer key. Keep write tools out unless the workflow needs supported mutations.
Add to Claude
Use the signed connector URL for Claude custom connectors, or the hosted MCP endpoint with an Authorization header in Claude Code.
Related pages
Deeper setup and reference material.
Use these pages for setup, tool coverage, and client-specific configuration details.
Connect Amazon Ads to Claude
Step-by-step answer page for using agentcentral to connect Amazon Ads data to Claude.
Open pageAmazon Ads MCP server
General Amazon Ads MCP page for campaigns, search terms, budget pacing, TACOS, and source fields.
Open pageAmazon MCP server for Claude
Claude page covering Amazon Ads plus Seller Central, inventory, orders, catalog, ranking, finance, and fulfillment data.
Open pageClaude quickstart
Configure Claude custom connectors or Claude Code with the hosted MCP endpoint.
Open pageAmazon Ads tool reference
Parameter-level reference for Amazon Ads MCP tools and source-provided fields.
Open pageAmazon Seller Central MCP
Seller Central MCP overview for the full hosted Amazon seller data layer.
Open pageAmazon seller MCP servers
Landscape page for official Ads MCP, Seller Central connectors, automation MCPs, and hosted seller data layers.
Open pageAmazon seller data layer
Data-layer explanation for agents reading normalized Amazon seller records across domains.
Open pageExample prompts
What an AI client can ask for.
Ask for source fields, date windows, and explicit metrics. agentcentral returns the data surface; the AI client reasons over it.
FAQ
Common questions.
What Amazon Ads MCP server works with Claude?+
agentcentral works as a hosted Amazon Ads MCP server for Claude. It exposes Amazon Ads campaign, keyword, search term, placement, budget, TACOS, and source-provided bid or budget suggestion fields through MCP.
Can Claude connect to Amazon Ads through MCP?+
Yes. Connect Amazon Ads in agentcentral, create a scoped Claude connector URL or MCP key, then add the hosted MCP server to Claude. The endpoint for header-capable clients is https://mcp.agentcentral.to/mcp.
Does this require a local MCP server?+
No. agentcentral hosts the MCP server. Claude custom connectors use a signed connector URL from the dashboard, and Claude Code can use the remote MCP endpoint with an Authorization bearer key.
Can Claude read Amazon Ads and inventory together?+
Yes, when the key includes the relevant domains. agentcentral can expose Amazon Ads, inventory, orders, catalog, ranking, finance, and fulfillment data through one hosted MCP server.
Does agentcentral decide bid changes?+
No. agentcentral is a data layer. It returns Amazon Ads source fields, deterministic metrics, retained history, source-provided suggestion fields, and audited write results. Claude or the customer-side workflow decides how to use that data.
Can write tools be disabled for Claude?+
Yes. A Claude key can be read-only or ads-read-only. Supported ads write tools are only available when the scoped key includes them.
Use agentcentral as the Amazon seller data layer.
Start a 7-day free trial, connect Amazon, and create a scoped MCP key or connector URL for the AI client you use.