Connect Amazon Vendor Central to Gemini CLI via MCP

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

Amazon Vendor Central + Gemini

Amazon Vendor Central through the Selling Partner API: retail purchase orders, acknowledgements, shipment confirmations, invoices, Direct Fulfillment orders with labels, packing slips and inventory, transaction status and vendor reports. Login with Amazon refresh token of a private vendor app.

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:

SPAPI_CLIENT_ID, SPAPI_CLIENT_SECRET, SPAPI_REFRESH_TOKEN, SPAPI_ENDPOINT, SPAPI_MARKETPLACE_ID

Step 1 — Get credentials

Setting up takes about 20 minutes. You need the plus Amazon's review of the developer profile.

1. In Vendor Central open Integration, then API Integration, and complete the Developer Profile. Under Data Access choose Private Developer: I build application(s) that integrate my own company with Amazon Services APIs, pick the roles you need and choose Register. Amazon reviews the profile and opens a case with the next steps.
2. On the same page choose Add new app client, complete the form, tick Vendors where Amazon offers the choice, and select the roles. Then choose View under LWA credentials and copy the client identifier into SPAPI_CLIENT_ID and the client secret into SPAPI_CLIENT_SECRET.
3. Choose Authorize app for your vendor account. Amazon shows a refresh token (it starts with Atzr|): paste it into SPAPI_REFRESH_TOKEN.
4. Pick your region in SPAPI_ENDPOINT (North America, Europe or Far East) and enter the marketplace id of your Amazon store in SPAPI_MARKETPLACE_ID, for example ATVPDKIKX0DER (US), A1PA6795UKMFR9 (Germany), A1F83G8C2ARO7P (UK), APJ6JRA9NG5V4 (Italy), A13V1IB3VIYZZH (France), A1RKKUPIHCS9HS (Spain), A1VC38T7YXB528 (Japan).

Roles: the retail tools need the role Amazon Fulfillment. The Direct Fulfillment tools need Direct-to-Consumer Shipping (Restricted), a restricted role because the orders carry customer addresses; Amazon asks for more information about data protection before granting it. The vendor reports need Brand Analytics. A call without its role answers 403.

Where to start: amazon_vendor_list_purchase_orders with purchase_order_state New shows what Amazon ordered; amazon_vendor_get_purchase_order gives one order in full.

Retail procurement: amazon_vendor_list_purchase_orders, amazon_vendor_get_purchase_order, amazon_vendor_list_purchase_order_statuses (accepted and received quantities). Answer an order with amazon_vendor_submit_acknowledgements, announce the shipment with amazon_vendor_submit_shipment_confirmations, and follow it with amazon_vendor_list_shipments and amazon_vendor_list_transport_labels. Acknowledgements and shipment confirmations are binding answers to Amazon, so amazon_vendor_submit_acknowledgements and amazon_vendor_submit_shipment_confirmations are installed switched off, as is amazon_vendor_submit_invoices: switch them on on the connector page when the AI should send them; it asks you to confirm every one.

Direct Fulfillment (you ship to Amazon's customer): amazon_vendor_list_df_orders, amazon_vendor_get_df_order, amazon_vendor_acknowledge_df_orders, amazon_vendor_list_df_packing_slips, amazon_vendor_get_df_packing_slip, amazon_vendor_list_df_customer_invoices, amazon_vendor_list_df_shipping_labels, amazon_vendor_get_df_shipping_label, amazon_vendor_submit_df_shipment_confirmations and amazon_vendor_update_df_inventory. Creating labels books transport: amazon_vendor_request_df_shipping_labels and amazon_vendor_create_df_shipping_labels are installed switched off, as are amazon_vendor_acknowledge_df_orders, amazon_vendor_submit_df_shipment_confirmations and amazon_vendor_submit_df_invoices.

Submissions are asynchronous: every submit tool answers with a transactionId and nothing else. Read the outcome with amazon_vendor_get_transaction_status (retail) or amazon_vendor_get_df_transaction_status (Direct Fulfillment): Processing, Success or Failure with the errors. Do not report a submission as done before it says Success.

Reports (3 steps): amazon_vendor_create_report, then amazon_vendor_get_report until DONE, then amazon_vendor_download_report_document.

Field notes: list calls cover at most 7 days per call; Direct Fulfillment lists need both created_after and created_before. Times are ISO 8601. Quantities come with a unit (Cases or Eaches for retail, Each for Direct Fulfillment); money is a decimal string with a currency code. partyId is your vendor code for the selling party and a warehouse code for ship-from and ship-to parties. Lists page with pagination.nextToken.

Rate limits: 10 calls per second per operation with a burst of 10 (transaction status: burst 20). On a 429 wait a moment and call again.

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 Gemini

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.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart gemini.
3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell) — anythingmcp should show as connected.
4. Start prompting — Gemini CLI can now call the Amazon Vendor Central tools.

Available tools

Example prompts

• "Which new Amazon purchase orders came in this week, and what quantities do they ask for?"
• "Show purchase order 2JK3S9VC with its items and ship window."
• "Which Direct Fulfillment orders still need a shipping label?"
• "Check transaction 12345-abcde: did Amazon accept the invoice I submitted?"
• "Request a vendor sales report for last week and tell me when it is ready."

FAQ

Where do the credentials come from? From a private app in Vendor Central (Integration, API Integration) after Amazon reviewed your Developer Profile. Copy the LWA client ID and secret, choose Authorize app to get the refresh token, and enter your region and marketplace id. No AWS keys are needed.

Which roles does it need? The retail tools need Amazon Fulfillment, the Direct Fulfillment tools the restricted role Direct-to-Consumer Shipping, and the reports Brand Analytics. It is for vendors (1P); sellers on Seller Central use the Amazon Seller Central connector.

Which tools install switched off? The binding answers to Amazon: amazon_vendor_submit_acknowledgements, amazon_vendor_submit_shipment_confirmations, amazon_vendor_submit_invoices, amazon_vendor_acknowledge_df_orders, amazon_vendor_request_df_shipping_labels, amazon_vendor_create_df_shipping_labels, amazon_vendor_submit_df_shipment_confirmations and amazon_vendor_submit_df_invoices. Switch them on on the connector page when the AI should send them.

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

• Connector landing page
• Connect to Claude