# Amazon Seller Central MCP connector

The Amazon Seller Central connector brings your inbound orders, warehouse inventory, shipments, and replenishment orders into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, where each person works inside their own Amazon Seller Central access.

Source: https://elaichi.ai/connectors/amazonseller/

## Facts

| | |
| --- | --- |
| Application | Amazon Seller Central |
| Category | Ecommerce |
| AI tools | 237 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Amazon Seller Central is connected

- Which inbound shipments are still waiting on transport details?
- List replenishment orders confirmed this week.
- Show current warehouse inventory and flag anything running low.

## Connect Amazon Seller Central in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Amazon Seller Central.
2. Optionally set Share with, then press Connect.
3. Paste your Amazon Seller Central app credentials. Amazon Seller Central authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Amazon Seller Central tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Amazon Seller Central MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Amazon Seller Central MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Amazon Seller Central MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Amazon Seller Central MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Amazon Seller Central MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Amazon Seller Central to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Amazon Seller Central tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Amazon Seller Central through Elaichi

### Check an inbound order before confirming it

Operations. Ask whether a batch is eligible for Amazon warehousing, then create and confirm the inbound order without opening a dozen Amazon Seller Central screens.

### Catch up shipments missing transport details

Logistics. List the inbound shipments still waiting on carrier and tracking information, then update the transport details for all of them in one go.

### Raise a replenishment order when stock runs low

Supply chain. Review current warehouse inventory, spot the products about to run out, and create and confirm the replenishment order from the same conversation.

### Print the right shipment labels first time

Warehouse. Find out which label page types apply to a shipment and pull the labels before the pallets reach the dock.

### Keep outbound orders moving

Ecommerce. See which outbound orders are open, adjust quantities on one that changed, and confirm it so the warehouse can pick it.

### Track Brazil shipment invoices

Finance. Check which Brazil shipments still need an invoice, create the missing ones, and report invoice status back to the team.

## Elaichi vs Zapier MCP vs Composio for Amazon Seller Central

All three can connect Amazon Seller Central to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Amazon Seller Central tools | Allow or restrict single Amazon Seller Central tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Amazon Seller Central call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Amazon Seller Central to Claude?

Connect Amazon Seller Central in Elaichi by entering your app credentials; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi as yourself, and Amazon Seller Central is ready to use.

### Does Amazon Seller Central work with ChatGPT and Cursor as well as Claude?

Yes. Once Amazon Seller Central is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Amazon Seller Central once and every client picks it up.

### What can an AI agent actually do with my Amazon Seller Central data?

It can look up inbound and outbound orders, check warehouse inventory, list shipments and their labels, update transport details, and create or confirm replenishment orders in Amazon Seller Central. It can also create and check Brazil shipment invoices. Short, concrete asks such as "list inbound shipments missing tracking" work better than long paragraphs.

### Does connecting Amazon Seller Central give the AI access to my whole seller account?

No. Every call to Amazon Seller Central runs inside the access of the person who signed in, so the agent sees only the orders, shipments, and inventory that person can already see. Elaichi can narrow that access further with restrictions, and it can never widen it.

### Can my team share one Amazon Seller Central connection?

Yes. One person connects Amazon Seller Central in Elaichi and shares it with a team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names who confirmed an order or updated a shipment.

### Can I stop an agent from deleting or changing things in Amazon Seller Central?

Yes. Restrictions in Elaichi work per action, so you can allow reading Amazon Seller Central inventory while restricting cancelling inbound orders, set on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Amazon Seller Central connection when someone leaves?

Offboarding that person in Elaichi ends their access to Amazon Seller Central at once, across every client they used. A shared Amazon Seller Central connection keeps working for everyone else on the team. If you disconnect Amazon Seller Central once in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client together.

### Does the Amazon Seller Central MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Amazon Seller Central is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Amazon Seller Central?

Yes. Both let Claude, ChatGPT or Cursor use Amazon Seller Central. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Amazon Seller Central call.

### How is Elaichi different from Composio for Amazon Seller Central?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Amazon Seller Central: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 237 Amazon Seller Central tools

Every tool below is callable through https://api.elaichi.ai/mcp once Amazon Seller Central is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Amazon Seller Central awd inbound eligibility check** (Create). Determines if the packages you specify are eligible for an AWD inbound order and contains error details for ineligible packages. Required: packagesToInbound. Default rate limit: 1 requests/second, burst 1.
- **Create a Amazon Seller Central awd inbound order** (Create). Creates a draft AWD inbound order with a list of packages for inbound shipment. The operation creates one shipment per order. Required: originAddress, packagesToInbound. Default rate limit: 1 requests/second, burst 1.
- **Get single Amazon Seller Central awd inbound order by ID** (Get). Retrieves an AWD inbound order. Required: id. Default rate limit: 2 requests/second, burst 2.
- **Update a Amazon Seller Central awd inbound order by ID** (Update). Updates an AWD inbound order that is in `DRAFT` status and not yet confirmed. Use this operation to update the `packagesToInbound`, `originAddress` and `preferences` attributes. Required: id, createdAt, orderId, orderStatus, originAddress, packagesToInbound. Default rate limit: 1 requests/second, burst 1.
- **Amazon Seller Central awd inbound orders cancel** (Cancel). Cancels an AWD Inbound order and its associated shipment. Required: order_id. Default rate limit: 1 requests/second, burst 1.
- **Amazon Seller Central awd inbound orders confirm** (Action). Confirms an AWD inbound order in `DRAFT` status. Required: order_id. Default rate limit: 1 requests/second, burst 1.
- **List all Amazon Seller Central awd inbound shipment label page types** (List). Retrieves the available label page types for a shipment ID that you specify. This is an asynchronous operation. If the label status is `GENERATED`, then the pageTypes are available. Required: shipment_id. Default rate limit: 1 requests/second, burst 2.
- **List all Amazon Seller Central awd inbound shipment labels** (List). Retrieves the box labels for a shipment ID that you specify. This is an asynchronous operation. If the label status is `GENERATED`, then the label URL is available. Required: shipment_id. Default rate limit: 1 requests/second, burst 2.
- **Amazon Seller Central awd inbound shipment transport details bulk update** (Update). Updates transport details for an AWD shipment. Required: shipment_id, trackingDetails. Default rate limit: 1 requests/second, burst 1.
- **Get single Amazon Seller Central awd inbound shipment by ID** (Get). Retrieves an AWD inbound shipment. Required: id. Default rate limit: 2 requests/second, burst 2.
- **List all Amazon Seller Central awd inbound shipments** (List). Retrieves a summary of all the inbound AWD shipments associated with a merchant, with the ability to apply optional filters. Default rate limit: 1 requests/second, burst 1. The connector follows `nextToken` through every page (sent back as `nextToken`).
- **List all Amazon Seller Central awd inventory** (List). Lists AWD inventory associated with a merchant with the ability to apply optional filters. Default rate limit: 2 requests/second, burst 2. The connector follows `nextToken` through every page (sent back as `nextToken`).
- **List all Amazon Seller Central awd outbound orders** (List). Retrieves all outbound AWD orders (with optional filters) that pertain to a merchant. By default, orders are sorted by the `updatedAt` attribute in descending order. Default rate limit: 1 requests/second, burst 1. The connector follows `nextToken` through every page (sent back as `nextToken`).
- **Create a Amazon Seller Central awd outbound order** (Create). Creates a draft AWD outbound order with the specified products. The API returns the order ID for the newly created order and starts an async validation check on the outbound products. After the validation check, the order status transitions from `VALIDATING` to `ELIGIBLE/INELIGIBLE`. Default rate limit: 1 requests/second, burst 1.
- **Get single Amazon Seller Central awd outbound order by ID** (Get). Retrieves an AWD outbound order with a set of shipments that contain items that are outbound into a destination channel. If the order is not eligible, the validation errors field is included in the order response. Required: id. Default rate limit: 1 requests/second, burst 1.
- **Update a Amazon Seller Central awd outbound order by ID** (Update). Updates an AWD outbound order that is in `DRAFT`, `ELIGIBLE`, or `INELIGIBLE` status. This API allows updates on `productsToOutbound` and `orderPreferences` attributes only. Any updates will restart the outbound order validation. Required: id, orderId, orderStatus, outboundShipments. Default rate limit: 1 requests/second, burst 1.
- **Amazon Seller Central awd outbound orders confirm** (Action). Confirms an AWD outbound order for a set of shipments that contain items that must be outbound to a destination node. You can confirm the order only if it's in an`ELIGIBLE` state. Required: order_id. Default rate limit: 1 requests/second, burst 1.
- **List all Amazon Seller Central awd replenishment orders** (List). Retrieves all the AWD replenishment orders pertaining to a merchant with optional filters. API by default will sort orders by updatedAt attribute in descending order. The connector follows `nextToken` through every page (sent back as `nextToken`).
- **Create a Amazon Seller Central awd replenishment order** (Create). Creates an AWD replenishment order with given products to replenish. The API will return the order ID of the newly created order and also start an async validation check on the products to e. The order status will transition to ELIGIBLE/INELIGIBLE status from VALIDATING post validation check.
- **Get single Amazon Seller Central awd replenishment order by ID** (Get). Retrieves an AWD Replenishment order with a set of shipments containing items that is/was planned to be replenished into an FBA node. Required: id.
- **Amazon Seller Central awd replenishment orders confirm** (Action). Confirms an AWD replenishment order in ELIGIBLE state with a set of shipments containing items that are needed to be replenished to an FBA node. Order can only be confirmed in ELIGIBLE state. Required: order_id.
- **List all Amazon Seller Central brazil shipment invoice statuses** (List). Returns the invoice status for the shipment you specify. Required: shipment_id. Default rate limit: 1.133 requests/second, burst 25.
- **Create a Amazon Seller Central brazil shipment invoice** (Create). Submits a shipment invoice document for a given shipment. Required: shipment_id, ContentMD5Value, InvoiceContent. Default rate limit: 1.133 requests/second, burst 25.
- **Get single Amazon Seller Central brazil shipment by ID** (Get). Returns the shipment details required to issue an invoice for the specified shipment. Required: id. Restricted operation (returns PII): get a Restricted Data Token with restricted_data_tokens.create for this path and pass it as the restricted_data_token query parameter. Default rate limit: 1.133 requests/second, burst 25.
- **List all Amazon Seller Central catalog items** (List). Search for a list of Amazon catalog items and item-related information. You can search by identifier or by keywords. Required: marketplaceIds. Default rate limit: 2 requests/second, burst 2. The connector follows `pagination.nextToken` through every page (sent back as `pageToken`).
- **Get single Amazon Seller Central catalog item by ID** (Get). Retrieves details for an item in the Amazon catalog. Required: id, marketplaceIds. Default rate limit: 2 requests/second, burst 2.
- **List all Amazon Seller Central competitive prices** (List). Returns competitive pricing information for a seller's offer listings based on seller SKU or ASIN. **Note:** The parameters associated with this operation may contain special characters that require URL encoding to call the API. To avoid errors with SKUs when encoding URLs, refer to URL Encoding. Required: MarketplaceId, ItemType. Default rate limit: 0.5 requests/second, burst 1.
- **Create a Amazon Seller Central competitive summary batch** (Create). Returns the competitive summary response, including featured buying options for the ASIN and `marketplaceId` combination. Required: requests. Default rate limit: 0.033 requests/second, burst 1.
- **Get single Amazon Seller Central data kiosk document by ID** (Get). Returns the information required for retrieving a Data Kiosk document's contents. See the `createQuery` operation for details about document retention. Required: id. Default rate limit: 0.0167 requests/second, burst 15.
- **List all Amazon Seller Central data kiosk queries** (List). Returns details for the Data Kiosk queries that match the specified filters. See the `createQuery` operation for details about query retention. Default rate limit: 0.0222 requests/second, burst 10. The connector follows `pagination.nextToken` through every page (sent back as `paginationToken`).
- **Create a Amazon Seller Central data kiosk query** (Create). Creates a Data Kiosk query request. **Note:** The retention of a query varies based on the fields requested. Each field within a schema is annotated with a `@resultRetention` directive that defines how long a query containing that field will be retained. Required: query. Default rate limit: 0.0167 requests/second, burst 15.
- **Delete a Amazon Seller Central data kiosk query by ID** (Delete). Cancels the query specified by the `queryId` parameter. Only queries with a non-terminal `processingStatus` (`IN_QUEUE`, `IN_PROGRESS`) can be cancelled. Cancelling a query that already has a `processingStatus` of `CANCELLED` will no-op. Required: id. Default rate limit: 0.0222 requests/second, burst 10.
- **Get single Amazon Seller Central data kiosk query by ID** (Get). Returns query details for the query specified by the `queryId` parameter. See the `createQuery` operation for details about query retention. Required: id. Default rate limit: 2.0 requests/second, burst 15.
- **Amazon Seller Central easy ship handover slots search** (Search). Returns time slots available for Easy Ship orders to be scheduled based on the package weight and dimensions that the seller specifies. This operation is available for scheduled and unscheduled orders based on marketplace support. See **Get Time Slots** in the Marketplace Support Table. Required: marketplaceId, amazonOrderId, packageDimensions, packageWeight. Default rate limit: 1 requests/second, burst 5.
- **Create a Amazon Seller Central easy ship package batch** (Create). This operation automatically schedules a time slot for all the `amazonOrderId`s given as input, generating the associated shipping labels, along with other compliance documents according to the marketplace (refer to the marketplace document support table). Required: marketplaceId, orderScheduleDetailsList, labelFormat. Restricted operation (returns PII): get a Restricted Data Token with restricted_data_tokens.create for this path and pass it as the restricted_data_token query parameter. Default rate limit: 1 requests/second, burst 5.
- **List all Amazon Seller Central easy ship packages** (List). Returns information about a package, including dimensions, weight, time slot information for handover, invoice and item information, and status. Required: amazonOrderId, marketplaceId. Default rate limit: 1 requests/second, burst 5. Returns one package, not a list.

- **Create a Amazon Seller Central easy ship package** (Create). Schedules an Easy Ship order and returns the scheduled package information. This operation does the following: * Specifies the time slot and handover method for the order to be scheduled for delivery. * Updates the Easy Ship order status. * Generates a shipping label and an invoice. Required: amazonOrderId, marketplaceId, packageDetails. Default rate limit: 1 requests/second, burst 5.
- **Amazon Seller Central easy ship packages bulk update** (Update). Updates the time slot for handing over the package indicated by the specified `scheduledPackageId`. You can get the new `slotId` value for the time slot by calling the `listHandoverSlots` operation before making another `patch` call. Required: marketplaceId, updatePackageDetailsList. Default rate limit: 1 requests/second, burst 5.
- **List all Amazon Seller Central expected payouts** (List). Returns the upcoming expected payouts from Amazon associated with a partner's account for the specified parameters. Default rate limit: 0.5 requests/second, burst 10. The connector follows `nextToken` through every page (sent back as `nextToken`).
- **List all Amazon Seller Central fba inbound delivery challan documents** (List). Provide delivery challan document for PCP transportation in IN marketplace. Required: inbound_plan_id, shipment_id. Default rate limit: 2 requests/second, burst 6.
- **List all Amazon Seller Central fba inbound delivery window options** (List). Retrieves all delivery window options for a shipment. Delivery window options must first be generated by the `generateDeliveryWindowOptions` operation before becoming available. Required: inbound_plan_id, shipment_id. Default rate limit: 2 requests/second, burst 30. The connector follows `pagination.nextToken` through every page (sent back as `paginationToken`).
- **Create a Amazon Seller Central fba inbound delivery window option** (Create). Generates available delivery window options for a given shipment. Required: inbound_plan_id, shipment_id. Default rate limit: 2 requests/second, burst 30.
- **Amazon Seller Central fba inbound delivery window options confirm** (Action). Confirms the delivery window option for chosen shipment within an inbound plan. A placement option must be confirmed prior to use of this API. Once confirmed, new delivery window options cannot be generated, but the chosen delivery window option can be updated before shipment closure. Required: inbound_plan_id, shipment_id, delivery_window_option_id. Default rate limit: 2 requests/second, burst 30.
- **List all Amazon Seller Central fba inbound eligibility previews** (List). This operation gets an eligibility preview for an item that you specify. You can specify the type of eligibility preview that you want (INBOUND or COMMINGLING). For INBOUND previews, you can specify the marketplace in which you want to determine the item's eligibility. Required: asin, program. Default rate limit: 1 requests/second, burst 1.
- **List all Amazon Seller Central fba inbound item compliance details** (List). List the inbound compliance details for MSKUs in a given marketplace. **Note:** MSKUs that contain certain characters must be encoded. For more information, refer to URL Encoding. Required: mskus, marketplaceId. Default rate limit: 2 requests/second, burst 6.
- **Amazon Seller Central fba inbound item compliance details bulk update** (Update). Update compliance details for a list of MSKUs. The details provided here are only used for the India (IN - A21TJRUUN4KGV) marketplace compliance validation. Required: marketplaceId, msku, taxDetails. Default rate limit: 2 requests/second, burst 6.
- **Create a Amazon Seller Central fba inbound item label** (Create). For a given marketplace - creates labels for a list of MSKUs. Required: labelType, marketplaceId, mskuQuantities. Default rate limit: 2 requests/second, burst 30.
- **Get single Amazon Seller Central fba inbound operation by ID** (Get). Gets the status of the processing of an asynchronous API call. Required: id. Default rate limit: 2 requests/second, burst 6.
- **List all Amazon Seller Central fba inbound packing group boxes** (List). Retrieves a page of boxes from a given packing group. These boxes were previously provided through the `setPackingInformation` operation. This API is used for workflows where boxes are packed before Amazon determines shipment splits. Required: inbound_plan_id, packing_group_id. Default rate limit: 2 requests/second, burst 30. The connector follows `pagination.nextToken` through every page (sent back as `paginationToken`).
- **List all Amazon Seller Central fba inbound packing group items** (List). Retrieves a page of items in a given packing group. Packing options must first be generated by the corresponding operation before packing group items can be listed. Required: inbound_plan_id, packing_group_id. Default rate limit: 2 requests/second, burst 30. The connector follows `pagination.nextToken` through every page (sent back as `paginationToken`).
- ...and 187 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
