Connect Amazon Seller Central to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Amazon Seller Central (SP-API), paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Amazon Seller Central + Microsoft Copilot

Ask Copilot about your Amazon business in plain language — "how many orders yesterday?", "which FBA SKUs are running low?", "do I still own the buy box on my bestseller?" — powered by Amazon's official Selling Partner API and your own private app credentials.

Prerequisites

A professional Seller Central account and a (free) self-authorized SP-API app. The connector needs these environment variables:

SPAPI_CLIENT_ID, SPAPI_CLIENT_SECRET, SPAPI_REFRESH_TOKEN, SPAPI_ENDPOINT, SPAPI_MARKETPLACE_ID, SPAPI_SELLER_ID

Step 1 — Get credentials

1. Seller Central → Apps & Services → Develop Apps (first time: complete the developer profile; Amazon reviews it manually).
2. Add new app client → type Sellers → select roles ("Inventory and Order Tracking", "Pricing", "Amazon Fulfillment", "Finance and Accounting"). No restricted PII roles needed. For the listings, listing restrictions and product type tools also select "Product Listing"; for review requests, "Buyer Solicitation". App created earlier without them? Add the roles, authorize the app again and use the new refresh token.
3. View → copy Client ID and Client Secret (LWA credentials).
4. Authorize → copy the Refresh Token (Atzr|…).
5. SPAPI_ENDPOINT: https://sellingpartnerapi-eu.amazon.com (EU), -na (Americas) or -fe (JP/AU/SG). SPAPI_MARKETPLACE_ID: e.g. DE A1PA6795UKMFR9, US ATVPDKIKX0DER. SPAPI_SELLER_ID: your Merchant Token (Account Info).

The connector performs the Login-with-Amazon OAuth2 exchange automatically and sends the 1-hour access token in the x-amz-access-token header — no AWS keys, no SigV4.

Listings and review requests: the connector also searches your listings and creates, changes or deletes them by SKU (price, merchant-fulfilled quantity, title, bullet points), with a preview mode that only validates a change; checks whether you may list an ASIN; looks up product types and their attribute rules; and sends Amazon's templated review request for an order. amazon_seller_delete_listings_item and amazon_seller_request_product_review are installed switched off, because a deleted listing and a sent review email cannot be undone: switch them on deliberately on the connector page. The AI asks before every change.

Already installed? The new tools reach a connector you installed earlier through its catalog update: open the connector in AnythingMCP and, under Catalog update available, check the list of new tools and click Apply update. Your credentials and any tools you added yourself stay as they are, and the delete and review request tools arrive switched off, as on a new install.

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

Open the connector store, import Amazon Seller Central (SP-API), fill in the env vars, and assign it to an MCP server.

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 Seller Central 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

• "Summarize yesterday's orders: count, revenue, cancellations."
• "Which FBA SKUs have fewer than 10 fulfillable units?"
• "Who owns the buy box for B08N5WRWNW and at what price?"
• "Estimate Amazon fees for this ASIN at €24.99 and compute my margin at €9.50 cost."
• "Set the price of SKU ABC-123 to €21.99, but run a validation preview first."
• "Which of my listings have errors, and what does Amazon say is wrong?"

Notes

• Buyer names/addresses (PII) are not exposed — that requires Amazon's Restricted Data Token and an approved restricted role. Order analytics work without it.
• Listing changes act on your live Amazon listings: try a change with mode: VALIDATION_PREVIEW first to see the issues it would cause without applying it. Bulk uploads (feeds) and free-text buyer messages are not covered.
• Test safely first: set SPAPI_ENDPOINT to https://sandbox.sellingpartnerapi-eu.amazon.com for canned sandbox responses.

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

• Turn Amazon Seller Central into an MCP server — full guide
• Automate your Amazon business with AI — real workflows
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse