Skip to content
<- All docs

MCP Connections

How to Connect Amazon Vendor Central to Claude

How to connect Amazon Vendor Central to Claude: add the Kuudo Vendor Central MCP as a custom connector, pick the vendor code, and work on POs and invoices.

Updated Oct 20, 2026 7 min read

Claude connects to Amazon Vendor Central through the Kuudo Amazon Vendor Central MCP server, which turns the vendor side of the Selling Partner API into tools Claude can call. Add the server's signed connector URL as a custom connector in Claude, switch it on in a chat, and name the vendor code and marketplace. Claude then works on your live purchase orders, shipments and invoices.

Reads change nothing. A write, such as acknowledging a purchase order, applies your workspace policy first, which can require a person to approve it. These steps cover Claude on the web and Claude Desktop; to connect Vendor Central to Claude Code, use the Claude Code quick start.

Your MCP server hostname is private to your deployment. Replace {your-private-mcp-host} with the private host shown in your dashboard.

What can Claude do in Vendor Central?

Amazon describes the vendor side of the Selling Partner API (SP-API) as web service integration for retail and direct fulfillment trading, usable instead of EDI (electronic data interchange) or beside it. Through it, Claude can work on:

  • Purchase orders: new orders, acknowledgements, cancellations and change orders.
  • Shipments: shipment requests, confirmations and labels.
  • Invoices: invoice submission and transaction status, so Claude can check that Amazon accepted what you sent.
  • Direct fulfillment: direct fulfillment orders, shipping and inventory.
  • Retail Analytics and catalog: Vendor Retail Analytics reports, Data Kiosk, Catalog Items, Listings Items and A+ Content, reached through the shared Selling Partner tools.

The Amazon Vendor Central MCP page lists the packages, and Amazon Vendor Central EDI explains how the API relates to an existing EDI setup.

What you need before connecting Vendor Central to Claude

  • A Kuudo workspace with the Amazon Vendor Central MCP server deployed, and access to its dashboard.
  • Your Vendor Central account authorized in Kuudo through the Selling Partner API with Login with Amazon. On Kuudo Pro and Kuudo Scale that runs through Kuudo's managed app, and an agency can send its client an authorization invitation; on Kuudo Community you connect your own Amazon app. See Amazon account authorization.
  • Claude on the web or Claude Desktop. Custom connectors work on every Claude plan, but Free allows only one, so Vendor Central beside Seller Central or Amazon Ads needs Pro, Max, Team or Enterprise.
  • On Team and Enterprise, an Owner adds the connector first under Organization settings > Connectors, and members then connect to it.

Connect Vendor Central to Claude

1. Copy the Vendor Central connector URL

In your Kuudo dashboard, open the Keys tab, create a key if needed, and copy the Claude connector URL for the Amazon Vendor Central MCP server. It is signed for Claude, so your API key never goes into Claude:

https://{your-private-mcp-host}/mcp/connect/{signed-token}

2. Add it as a custom connector

  1. In Claude, open Customize > Connectors.
  2. Click +, then Add custom connector.
  3. Name it amazon-vendor-central.
  4. Paste the signed URL and click Add.

Claude's form cannot attach an Authorization header, so it needs the signed URL rather than the plain /mcp endpoint.

3. Switch it on in a chat

Start a new chat, open Connectors from the composer and switch amazon-vendor-central on. When Claude asks to use a tool, read the request, and keep tools that acknowledge orders, confirm shipments or submit invoices on ask rather than Allow always.

4. Check the connection with a read-only question

Ask a question that reads your Vendor Central data without changing anything:

Which purchase orders arrived in the last 7 days? Don't acknowledge anything.

Claude should list recent purchase orders for the authorized vendor account. An access error usually means the Vendor Central account is not authorized yet.

Pick the vendor code and marketplace Claude works in

A vendor can hold several vendor codes, and Amazon runs Vendor Central in North America, Europe and the Far East. Name the code and marketplace you mean:

Work on vendor code ABCDE in the US marketplace for this chat.

An agency reaches each authorized client's vendor codes through the same connector, with each code's access kept to itself.

First Vendor Central tasks to try in Claude

  • Open acknowledgements: "Which purchase orders are still waiting for acknowledgement, and when are they due?"
  • Invoice status: "Did Amazon accept the invoices we submitted last week? List any that failed and why."
  • Direct fulfillment: "Which direct fulfillment orders must ship today?"
  • Retail Analytics: "Pull last week's Retail Analytics sales by ASIN." The Retail Analytics sales dashboard guide shows what to build from it.

Troubleshooting Vendor Central in Claude

Claude sees no purchase orders

The connector works, but the Vendor Central account is not authorized for your workspace yet, or no orders arrived in the window you asked about. Authorize the account in Kuudo, or widen the date range.

A vendor code or marketplace is missing

The authorization covers the vendor codes and regions it was granted for. Authorize the missing code or region in Kuudo, then ask again.

A Retail Analytics report is still pending

Amazon builds these reports asynchronously and decides how long each takes and whether it completes. Ask Claude to check the report's status later rather than requesting it again.

The custom connector will not add, or returns 401

Use the signed Claude connector URL from the Keys tab, not the plain /mcp endpoint. For a 401, create a fresh key, copy a new signed URL and replace the connector.

Frequently asked questions

Can Claude acknowledge purchase orders or submit invoices?

Yes, within the scope of the credentials you grant. Reads change nothing; a write, such as acknowledging a purchase order, applies your workspace policy first, which can require a person to approve it. Claude also asks before it calls a tool unless you chose Allow always.

Does it include Retail Analytics?

Yes. Vendor Retail Analytics reports, Data Kiosk and A+ Content reach vendor data through the shared Selling Partner tools your deployment also exposes, so Claude can pull sales, traffic and inventory reports beside purchase orders. Amazon builds each report asynchronously and decides how long it takes.

Which regions are supported?

North America, Europe and the Far East. Access is vendor-scoped and authenticated with Login with Amazon.

Can an agency work across several vendor codes?

Yes. The Vendor Central MCP is built for brands, agencies running many vendor codes and consultants standing up new clients, and keeps each code's access to itself. Name the vendor code and marketplace in the chat.

Can I connect Vendor Central and Seller Central to Claude together?

Yes. A brand that sells to Amazon as a vendor and on Amazon as a seller adds both servers as custom connectors and switches both on in one chat. Claude's Free plan allows only one custom connector, so two servers need Pro, Max, Team or Enterprise. See How to connect Amazon Seller Central to Claude and Vendor Central vs Seller Central.

<- Previous How to Connect Amazon Seller Central to Claude Next -> Connect Amazon Seller, Vendor and Ads to Claude Code