Skip to content

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.

  • App credentials
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which inbound shipments are still waiting on transport details?

Working in Amazon Seller Central with Elaichi

  • Get single Amazon Seller Central awd inbound order by ID
  • List all Amazon Seller Central awd inbound shipment label page types
  • List all Amazon Seller Central awd inbound shipment labels
Ask anything…
Governance / Audit log Last 24 hours
Amazon Seller Central List all Amazon Seller Central awd inbound shipment labels Emily Carter · Claude · 9:41 AM Done
Amazon Seller Central List all Amazon Seller Central awd inbound shipment label page types Emily Carter · Claude · 9:41 AM Done
Amazon Seller Central Get single Amazon Seller Central awd inbound order by ID Emily Carter · Claude · 9:41 AM Done
Amazon Seller Central Create a Amazon Seller Central awd inbound eligibility check Megan Brooks · ChatGPT · 9:38 AM Done
Amazon Seller Central Create a Amazon Seller Central awd inbound order Ryan Hayes · Cursor · 9:35 AM Done

How to connect Amazon Seller Central to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Amazon Seller Central MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ 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

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 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

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Amazon Seller Central MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

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

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

What teams do with Amazon Seller Central through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Amazon Seller Central is logged.

  • Operations

    Check an inbound order before confirming it

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

  • Logistics

    Catch up shipments missing transport details

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

  • Supply chain

    Raise a replenishment order when stock runs low

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

  • Warehouse

    Print the right shipment labels first time

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

  • Ecommerce

    Keep outbound orders moving

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

  • Finance

    Track Brazil shipment invoices

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

Try asking

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

See all 237 Amazon Seller Central tools →

What connecting Amazon Seller Central gets you

6 screens from Elaichi, each doing one job for your Amazon Seller Central account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which inbound shipments are still waiting on transport details?

List replenishment orders confirmed this week.

Show current warehouse inventory and flag anything running low.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about inbound orders in plain language.

Check shipment status, inventory levels, and replenishment orders from live Amazon Seller Central records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint for every client you use.

Claude, ChatGPT, and Cursor reach Amazon Seller Central through one governed endpoint, no shared key.

ElaichiTools
Tool Action Description
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.

Tool catalog

237 Amazon Seller Central tools, no code required.

Inbound orders, outbound orders, inventory, shipments, labels, and invoices are covered out of the box.

ElaichiToolboxes
Name Source template Tools Created

Operations toolbox

Amazon Seller Central · inbound orders and shipments

Amazon Seller Central starter 18 Mar 4, 2026

Supply chain toolbox

Amazon Seller Central · replenishment orders and inventory

— 9 Mar 2, 2026

Logistics toolbox

Amazon Seller Central · shipment labels and transport details

— 24 Feb 27, 2026

Finance toolbox

Amazon Seller Central · shipment invoices

Amazon Seller Central starter 6 Feb 19, 2026

Ecommerce toolbox

Amazon Seller Central · outbound orders

— 31 Jan 30, 2026

Warehouse toolbox

Amazon Seller Central · inventory and inbound eligibility

— 12 Jan 22, 2026

Toolboxes

Each team gets its own toolbox.

Operations sees inbound orders, finance sees invoices, each toolbox scoped to one team.

ElaichiConnections
Connection Scope Status Access
AM

Amazon Seller Central (Operations)

Connected by Emily Carter

Personal • Active 1 team · 6 members
AM

Amazon Seller Central (Supply chain)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
AM

Amazon Seller Central (Logistics)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
AM

Amazon Seller Central (Finance)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
AM

Amazon Seller Central (Brazil)

Connected by Ryan Hayes

Personal • Active Not shared
AM

Amazon Seller Central (Fulfillment)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates work through a connection, never a credential.

One person connects Amazon Seller Central and shares it, and nobody else handles a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Amazon Seller Central Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Amazon Seller Central Inbound orders Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Amazon Seller Central Inbound orders List Toolbox

Audit log

Every call answers who did what.

When, who, what happened, and which shipment or order, in one append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Amazon Seller Central digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch inbound orders

    Amazon Seller Central

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Amazon Seller Central

    Queued

Workflows

A schedule starts real work, end to end.

Inbound orders are fetched and grouped, a digest is drafted, approved, then posted back.

Amazon Seller Central health

Refreshed 4 minutes ago · every 15 minutes · from the inbound orders collection

Live

Inbound orders

1,284 ↓ 12%

Outbound orders

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Inbound orders created

Last 14 days

By team

Share of activity

Operations 34%

Supply chain 27%

Logistics 21%

Finance 18%

Collections and dashboards

Inbound order numbers, computed without a model.

Four metrics, 14 days of orders created, and a breakdown by team, refreshed on schedule.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Amazon Seller Central, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Amazon Seller Central tools for your AI agents

237 tools are ready to call through Elaichi's MCP endpoint the moment you connect Amazon Seller Central, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 197 of 237 Amazon Seller Central tools here. Connect Amazon Seller Central and call search_tools or tools/list over the MCP endpoint for the complete set.

Questions, answered

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.

Put Amazon Seller Central in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot