Amazon Selling Central MCP
Related Servers
Alternatives to Amazon Selling Central MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables managing Amazon seller listings, orders, pricing, inventory, and reports through the SP-API via MCP tools.1512 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server to interact with Amazon Ads11 npm29MIT
- AlicenseNot gradedqualityCmaintenanceEnables sellers to interact with Amazon Selling Partner API and Advertising API data—orders, inventory, pricing, ads, reports, and more—through MCP clients like Claude and Cursor.MIT
- FlicenseNot gradedqualityCmaintenanceUnifies Amazon SP-API and Ads API into 20 MCP tools for orders, inventory, reports, feeds, and advertising, handling auth, throttling, and PII compliance automatically.-
- AlicenseNot gradedqualityBmaintenanceHosted Amazon Seller Central & Vendor Central MCP server. Connect Claude, ChatGPT, Cursor, Codex, Gemini, and GitHub Copilot to live Amazon SP-API and Amazon Ads API data.15MIT
- AlicenseNot gradedqualityBmaintenanceConnects Amazon Seller Central and Amazon Advertising to any MCP client, with a settlement-accurate P&L underneath: every fee, refund and reimbursement as Amazon actually posted it, so contribution margin and breakeven are per product, per marketplace, per day. 107 tools spanning P&L, full Sponsored Products/Brands/Display management, Search Query Performance and Brand Analytics, inventory and for1MIT
TDQS
Scored across 303 tools
The tool set contains extensive duplication from multiple API versions: CatalogItems vs CatalogItems20201201, ListingsItems vs ListingsItems20200901, ProductPricing vs ProductPricing20220501, Replenishment vs Replenishment20221107, Orders vs Ordersv2, and Shipping vs ShippingLegacy all expose overlapping operations. An agent cannot easily determine which version to call, and some pairs like ExternalFulfillmentShipments_retrieveInvoice vs generateInvoice have nearly identical descriptions.
The dominant Domain_verbNoun pattern with snake_case is largely consistent across most tools (e.g., Orders_getOrder, Reports_createReport). However, Messaging breaks convention with PascalCase verbs in Messaging_GetAttributes, Messaging_CreateAmazonMotors, and Messaging_CreateWarranty, while Shipping_oneClickShipment mixes camelCase inside snake_case. The version-suffixed duplicates are predictable but add clutter.
303 tools is extreme by any measure, far beyond the threshold where agents can reliably navigate a tool surface. A large portion of the count comes from redundant versioned API copies (V0, 2020-12-01, 2022-05-01, 2022-11-07) that could be consolidated into a few dozen core operations. This count creates severe selection overhead.
The set nominally covers a broad range of Amazon selling domains—orders, listings, inventory, fulfillment, shipping, reports, feeds, pricing, finances, messaging, and notifications. However, every tool description states 'Runs in your Kuudo deployment, not here,' suggesting none of these are actually executable in this server, which is a fundamental dead end. Additionally, FbaInventory is limited to sandbox-only operations, leaving production inventory management gaps.