Amazon Orders MCP
Related Servers
Alternatives to Amazon Orders MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables downloading Amazon order history as CSV files with support for orders, items, shipments, and transactions across 16 Amazon regional sites using browser automation.1212 npm19MIT
- AlicenseNot gradedqualityAmaintenanceEnables read-only access to a user's Amazon.com.br purchase history, including orders, products, prices, shipping, promotions, reward points, installments, invoices, and spending summaries, with a local SQLite cache.6 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides read-only access to a user's AliExpress purchase history, including orders, products, price breakdowns, shipping, refunds, and spending summaries, with local caching.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to research and shop on Amazon using their own logged-in browser session, supporting product search, details, reviews, cart, wishlist, and order tracking without API keys.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.-
- AlicenseAqualityCmaintenanceEnables searching products, viewing orders, and analyzing order trends on Amazon.in via a persistent Playwright browser session.9-
TDQS
Scored across 5 tools
Each tool has a distinct action and target: list_accounts (read accounts), login_account (authenticate), sync_orders (import), get_orders (read local orders), remove_account (delete account). No overlapping purposes; descriptions clarify the read/write split between sync_orders and get_orders.
All tools use snake_case with a verb_noun pattern (list_accounts, login_account, sync_orders, get_orders, remove_account). Singular/plural noun variations (account vs accounts) are minor and do not break the pattern.
5 tools appropriately cover the core account and order management workflows without redundancy or excessive granularity. This is well within the ideal 3-15 range for a focused MCP server.
Core account lifecycle (list, login, remove) and order workflow (sync, get) are covered. Minor gaps exist: no tool to retrieve a single order by ID or search orders, and sync/get operations do not explicitly target a specific account, requiring workarounds via login switches.