Connect Amazon Ads to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Amazon Ads, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Amazon Ads + Microsoft Copilot

Read Amazon Ads (Sponsored Products) accounts: advertising profiles, campaigns, ad groups, product ads, keywords, negative keywords and targets, and request Reporting v3 performance reports for Sponsored Products, Brands and Display. For sellers, vendors and agencies, in the NA, EU and FE regions.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

AMAZON_ADS_CLIENT_ID, AMAZON_ADS_CLIENT_SECRET, AMAZON_ADS_API_URL, AMAZON_ADS_AUTHORIZATION_URL, AMAZON_ADS_TOKEN_URL

Step 1 — Get credentials

1. Make sure you have Amazon Ads API access: an approved API application and a Login with Amazon (LWA) security profile linked to it. You apply for API access with Amazon Ads (Partner Network, or https://advertising.amazon.com/API). Without API approval the sign-in works, but Amazon refuses every call.

2. In the LWA console (https://developer.amazon.com, Login with Amazon) open the security profile, then Web Settings, and add https://cloud.anythingmcp.com/api/mcp-oauth/callback (if you host AnythingMCP yourself: <your AnythingMCP URL>/api/mcp-oauth/callback) under Allowed Return URLs.

3. Copy the Client ID and the Client Secret (Show Secret) from the same page into AMAZON_ADS_CLIENT_ID and AMAZON_ADS_CLIENT_SECRET. The client ID starts with amzn1.application-oa2-client..

4. Set AMAZON_ADS_API_URL, AMAZON_ADS_AUTHORIZATION_URL and AMAZON_ADS_TOKEN_URL for your region, in that order:

   • North America (US, CA, MX, BR): https://advertising-api.amazon.com, https://www.amazon.com/ap/oa, https://api.amazon.com/auth/o2/token
   • Europe (UK, DE, FR, IT, ES, NL, SE, PL, TR, AE, SA, EG, IN): https://advertising-api-eu.amazon.com, https://eu.account.amazon.com/ap/oa, https://api.amazon.co.uk/auth/o2/token
   • Far East (JP, AU, SG): https://advertising-api-fe.amazon.com, https://apac.account.amazon.com/ap/oa, https://api.amazon.co.jp/auth/o2/token

   A connector only sees the profiles of its region, so install it once per region if you advertise in several.

5. Leave AMAZON_ADS_REFRESH_TOKEN empty, unless you already authorized this security profile for the Amazon Ads API elsewhere (that token starts with Atzr|). Install the connector, click Authorize with Provider and sign in with the Amazon account that has access to the advertising accounts. The scope is advertising::campaign_management.

6. Run amazon_ads_list_profiles. A profile is one advertiser in one marketplace, and its id goes into every other tool. An empty list means the account has no advertising account in this region or never created a campaign.

Read-only: the AI lists Sponsored Products campaigns, ad groups, product ads (the advertised ASINs or SKUs), keywords with bids and match types, negative keywords and product, category and auto targets.

Performance comes from reports: impressions, clicks, cost, sales, ACOS and ROAS are only available as reports. amazon_ads_create_report starts a report job on Amazon's side (it changes no campaign) and amazon_ads_get_report checks its status. Reports usually finish within minutes but can take up to an hour at busy times. Most report types look back 95 days, and a DAILY report covers at most 31 days. Sponsored Brands and Sponsored Display campaigns are not listed, but their performance is available through reports.

The report file: a finished report is a download link to a gzip-compressed JSON file, valid for about an hour. The connector cannot unpack that file, so the AI hands you the link to download and open it yourself, or to pass to a tool that can decompress it. Costs are in the profile's currency.

Limits and errors: Amazon throttles per account and endpoint and answers 429 with a time to wait before retrying. Access tokens last one hour and are renewed automatically. 401: authorize again, and check that the client ID, sign-in URL and token URL belong to the same region as the API endpoint. 403: the Amazon account has no access to that profile, or the security profile is not approved for the Amazon Ads API. 425: the same report was already requested, and the answer carries its id.

The connector does not create or change campaigns, bids or budgets, and does not list Sponsored Brands or Sponsored Display campaigns.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Amazon Ads tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "List our advertising profiles with their marketplace and currency."
• "Request a Sponsored Products report by campaign for the last 30 days and give me the download link when it is ready."
• "Which keywords in our manual campaigns use broad match, and what are their bids?"
• "Show the negative keywords of our biggest campaign so I can check for gaps before we add new ones."

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse