Amazon Ads MCP server

Sponsored Products, Brands and Display -- plus the analysis that explains a ROAS drop.

Connect Amazon Ads All connectors

Tools: 52
Read-only: 25
Write: 27; Off by default
Destructive: 2; Flagged distinctly

What it does

Amazon Ads through an assistant

Campaign management across all three Sponsored ad products, with Sponsored Products at full depth: campaigns, ad groups, product ads, keywords, negative keywords and product targets. On top of that sits a set of analysis tools that drive Amazon's async reporting for you -- period and year-over-year comparison, ROAS driver decomposition, seasonality, and a root-cause synthesis that pulls in retail context from a linked Selling Partner connection when one exists. Writes are opt-in, and any budget change needs a confirmed spend figure inside the same call.

Sponsored Products campaigns, ad groups, product ads, keywords and targets
Sponsored Brands and Sponsored Display campaigns, ad groups and targeting
Async report submission, polling and retrieval across all three ad products
Period, year-over-year and seasonality comparisons, ROAS driver decomposition and cross-connector root-cause analysis
Config-change history, snapshotted on demand -- Amazon exposes no such API
Create and update campaigns, ad groups, keywords and targets (opt-in)

Ask your assistant

What people actually ask

Real questions, answered from live Amazon Ads data.

“ROAS dropped last week -- what actually caused it?”

amazon_ads_roas_root_causeamazon_ads_roas_decomposition

“Compare Sponsored Products performance this month against the same month last year.”

amazon_ads_year_over_year_comparisonamazon_ads_performance

“Which campaigns had bids or budgets changed since the start of the quarter?”

amazon_ads_config_change_historyamazon_ads_management_transition_analysis

Tool catalogue

52 Amazon Ads tools

Grouped by what they touch. Every tool is individually toggleable — you expose only what you want.

Reporting & analytics

10 tools9 read-only · 1 write

Showing 10 of 10 tools

amazon_ads_create_report
Write
Request a performance report across Sponsored Products, Brands, or Display. Returns a report_id -- call amazon_ads_get_report_status to check when it's ready, then amazon_ads_get_report_result to fetch it. Report generation is asynchronous and can take minutes; this call returns immediately.
amazon_ads_get_report_result
Read-only
Fetch and parse a completed report's data. Returns 'not ready' if the report hasn't finished -- call amazon_ads_get_report_status first to check. Large reports are truncated to the first 2000 rows; check the returned total_rows/truncated fields.
amazon_ads_get_report_status
Read-only
Poll a report's generation status. Call amazon_ads_get_report_result once status is COMPLETED.
amazon_ads_management_transition_analysis
Read-only
Compares performance before/after a transition date across two campaign cohorts: campaigns with a recorded configuration change at or after the transition (treatment) vs. campaigns with none (control). Both cohorts deteriorating similarly suggests an external cause (seasonality/market demand); only the changed cohort deteriorating points at the changes themselves. REQUIRES prior amazon_ads_snapshot_config_history runs bracketing the transition date -- Amazon exposes no historical config-change API, so without local snapshot history this tool cannot form the cohorts and will say so rather than guess. Fetches one live performance report spanning both windows, which can take longer than one call allows -- see report_id for resuming.
amazon_ads_performance
Read-only
Live Sponsored Products performance for a date range -- impressions, clicks, spend, orders, units, sales, plus derived CTR/CPC/CVR/ACOS/ROAS/AOV, aggregated across the profile and broken out per campaign. Runs Amazon's report generation internally (this can take longer than one call allows) -- if the response has status 'processing', call this tool again with the same report_id to resume; do not start a new one.
amazon_ads_period_comparison
Read-only
Compares Sponsored Products performance between two arbitrary date ranges (raw counts and derived CTR/CPC/CVR/ACOS/ROAS/AOV, each with before/after/absolute-change/percent-change). Fetches one report spanning both periods, which can take longer than one call allows -- see report_id for resuming.
amazon_ads_roas_decomposition
Read-only
Decomposes a ROAS change between two periods into its CPC/CVR/AOV drivers using exact logarithmic decomposition (each driver's contribution sums exactly to the total change -- no residual/interaction term). Fetches one report spanning both periods, which can take longer than one call allows -- see report_id for resuming.
amazon_ads_roas_root_cause
Read-only
Diagnoses WHY ROAS changed between two periods -- classifies as seasonality_dominant / management_dominant / retail_dominant / mix_shift / mixed / inconclusive, with evidence and (when supported) a quantitative seasonality-vs-management contribution split. Fetches its own performance data plus, if a sibling Amazon SP-API connection exists in this workspace, retail context (Buy Box change) automatically. For the strongest diagnosis, call amazon_ads_management_transition_analysis, amazon_ads_year_over_year_comparison, and amazon_ads_seasonality_analysis FIRST and pass their raw output back in as management_transition/year_over_year/seasonality -- each is its own bounded Amazon report and can't all be fetched inside this one call. Without them, this tool still runs on ROAS comparison + driver decomposition + retail context alone, with lower confidence and a note on what's missing. Never turns correlation into certainty -- a quantitative contribution split is only produced when the underlying comparisons genuinely support one.
amazon_ads_seasonality_analysis
Read-only
Analyzes average ROAS/sales by calendar month across the requested history to surface recurring seasonal patterns. Requires at least 24 months of daily data to produce a conclusion -- with less, returns insufficient_history rather than guessing from one observation. This is the heaviest tool in this connector under ServeMCP's live-fetch model (no local historical warehouse): a multi-year daily report is large and MAY require multiple resumed calls (see report_id) before it completes.
amazon_ads_year_over_year_comparison
Read-only
Compares Sponsored Products performance for a date range against the same calendar dates exactly one year earlier. Fetches one report spanning both years, which can take longer than one call allows -- see report_id for resuming.

Profiles & accounts

2 tools2 read-only · 0 write

Showing 2 of 2 tools

amazon_ads_get_profile
Read-only
Retrieve an authorized profile's account details (country, currency, account type).
amazon_ads_list_accessible_profiles
Read-only
List every Amazon Ads profile (advertiser account) this connection's token can see, across all three regions (North America, Europe, Far East) -- not filtered to just the ones authorized on this connection. Use this to find profile IDs to authorize from Settings -> Connections -> Manage Profiles.

More tools

2 tools1 read-only · 1 write

Showing 2 of 2 tools

amazon_ads_config_change_history
Read-only
Reads previously-recorded configuration changes for a profile (from amazon_ads_snapshot_config_history runs). Only covers the period since snapshotting started for this connection -- Amazon exposes no way to reconstruct history from before the first snapshot. Read-only.
amazon_ads_snapshot_config_history
Write
Fetches this profile's current Sponsored Products campaign/ad-group/target configuration, diffs it against the most recent stored snapshot for this connection, and records what changed. Amazon has no historical config-change API, so this is the ONLY way ServeMCP can answer 'what changed and when' -- and history is only as complete as how often this tool is actually called. Run it regularly (or on a schedule via an external cron calling this tool) for meaningful history. Writes to ServeMCP's own database, not Amazon.

Every tool name and description, machine-readable: /llms-full.txt

Access & safety

You decide what it can touch

The same model applies to every connector, and it defaults closed.

Authorize once

Connect Amazon Ads through its own consent screen. Credentials are encrypted with AES-256-GCM and never returned by any API response or tool call.

Writes off by default

A new connection switches on a read-oriented default set only. Every write tool must be enabled deliberately before any client can call it.

Roles enforced server-side

READ, WRITE and ADMIN gate tool invocation on the server, not just in the UI. A READ member's token is refused any write tool.

Setup

Connect Amazon Ads in minutes

No infrastructure to run. Copy one URL and one token into your client.

1Create a free workspace and connect Amazon Ads.
2Choose which tools to expose — writes stay off until you enable them.
3Copy your MCP endpoint URL and bearer token.
4Paste them into Claude, Cursor, or any MCP client.

claude_desktop_config.json

{
  "mcpServers": {
    "serve-mcp": {
      "url": "https://servemcp.com/api/mcp/your-workspace",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer smcp_..."
      }
    }
  }
}