Amazon Seller Central MCP server (Amazon Selling Partner MCP) by Kuudo
One MCP for the entire Amazon Selling Partner API: 304 operations across 40+ services, from Catalog, Listings, and Orders to FBA and A+ Content.
Product page: https://www.kuudo.com/features/amazon-selling-partner-mcp/ · Docs: https://www.kuudo.com/docs/mcp-reference/amazon-sp-tools/ · Pricing: https://www.kuudo.com/pricing.md
Connect
Kuudo runs in your own cloud. The Community plan deploys one instance of each Amazon MCP server into your account, and your client connects to that deployment:
{
"mcpServers": {
"amazon-selling-partner-mcp": {
"url": "https://<your-host>/mcp",
"headers": {
"Authorization": "Bearer <your Kuudo API key>"
}
}
}
}
Replace <your-host> with the hostname of your deployment and the bearer value with your Kuudo API key.
What this repository is
This repository holds registry metadata and a catalog-only stub. Live execution runs in your Kuudo deployment. The server source is not published. The stub in src/ answers tools/list with the catalog below, serves the same catalog as one resource (kuudo://catalog/tools.json), offers one prompt (connect) carrying the setup guidance, and returns an error with that guidance on any call, so registries and clients can inspect the surface without any access to Amazon.
Inspect the catalog locally with Docker
The image runs the same catalog-only stub over stdio. It is not the live server.
docker build -t amazon-selling-partner-mcp .
docker run -i --rm amazon-selling-partner-mcp
Point a client at it with a stdio entry:
{
"mcpServers": {
"amazon-selling-partner-mcp-catalog": {
"command": "docker",
"args": ["run", "-i", "--rm", "amazon-selling-partner-mcp"]
}
}
}
Tools
304 API operations exposed as 303 tools across 51 Selling Partner API resources. Two operations share one name and collapse into one tool. The production server's built-in setup and status tools are not listed here.
Argument schemas are not published in this catalog: every tool carries an empty object schema, and the live server in your deployment validates the real parameters on each call.
Set up your client
- Quick Start: Activepieces MCP
- Quick Start: Google Antigravity
- Quick Start: ChatGPT Skills
- Quick Start: ChatGPT
- Quick Start: Claude
- Quick Start: Claude Skills
- Quick Start: Claude Code MCP
- Quick Start: Claude Cowork for Amazon Workflows
- Quick Start: Claude Code Skills
- Quick Start: Codex Skills
- Quick Start: Codex
- Quick Start: Hermes MCP
- Quick Start: Lovable
- Quick Start: n8n MCP
- Quick Start: NanoClaw MCP
- Quick Start: OpenAI API
- Quick Start: OpenClaw MCP
- Quick Start: Perplexity MCP
Playbooks
Operator guides grounded in Amazon's own documentation, each with the artifact the agent produces:
- Auditing FBA Reimbursements: What Amazon Owes You
- Diagnose a Suppressed Listing: Stranded to Buyable
- Recover Buy Box Eligibility: Causes and Fixes
- FBA Inventory Health: The Post-2024 Fee Playbook
- Brand Registry: Fix 'Trademark Already Enrolled'
- Seeded Image Upgrades: Regenerating Listing Visuals From Your Current Photos, With Approval Gates
- Amazon FBM Orders Reports: What to Request and Why
- End-to-End Listing Optimization: From Live-Data Audit to a Previewed, Confirmed Patch
How it compares
- Kuudo vs agentcentral for Amazon MCP
- Kuudo vs Pixii for Amazon sellers
- Amazon PPC software compared, tool by tool
Reads, writes, approvals
Read tools are safe to call freely. Write tools are guarded and can require approval before anything changes on Amazon. The full read-versus-write split is documented at https://www.kuudo.com/docs/mcp-reference/amazon-sp-tools/.
Kuudo
- Website: https://www.kuudo.com/
- Docs: https://www.kuudo.com/docs/
- Guides: https://www.kuudo.com/guides/
- Community, bugs, and questions: https://github.com/KuudoAI/community
- Roadmap: https://github.com/orgs/KuudoAI/projects
- Machine-readable: https://www.kuudo.com/llms.txt · https://www.kuudo.com/pricing.md
Generated from KuudoAI/marketing. Do not edit by hand; changes are overwritten on the next sync.
Smithery listing
See Smithery publishing for the hosted endpoint, API-key configuration, and discovery prerequisites.