Amazon FBA Ops MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LWA_APP_ID | Yes | Your Amazon LWA application client ID from Seller Central. | |
| LWA_CLIENT_SECRET | Yes | Your Amazon LWA client secret. | |
| SP_API_REFRESH_TOKEN | Yes | Your Amazon Selling Partner API refresh token obtained via self-authorization. | |
| SP_API_DEFAULT_MARKETPLACE | Yes | Your seller marketplace code (e.g., US, UK, DE, JP) matching your seller account. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ordersA | List Amazon orders created in a date range (YYYY-MM-DD). Optionally filter by order status (e.g. Shipped, Unshipped, Canceled). |
| get_order_itemsA | List the SKU/quantity/price line items for one Amazon order. |
| get_financial_eventsA | List Amazon financial events (fees, refunds, reimbursements) posted in a date range (YYYY-MM-DD). |
| calculate_profitabilityA | Compute profitability (revenue, Amazon fees, reimbursements, COGS, net profit, margin %) for a date range (YYYY-MM-DD), grouped by 'sku', 'order', or 'day'. Requires SKU costs to be set via set_sku_cost for accurate COGS -- SKUs missing a cost are flagged in 'missing_cogs_skus' rather than silently treated as zero-cost. |
| get_inventory_summaryA | Get current FBA inventory levels (fulfillable, inbound, reserved, unfulfillable quantities), optionally filtered to one SKU. |
| get_low_stock_alertsA | Flag SKUs at risk of stocking out soon, estimating days-of-supply from current fulfillable inventory and recent sales velocity (units sold over lookback_days). |
| get_catalog_itemA | Get a product's title, brand, image, and dimensions from the Amazon catalog by ASIN. |
| set_sku_costA | Record the cost-of-goods (COGS) for a SKU, used by calculate_profitability_tool. Amazon has no concept of product cost, so this must be maintained manually. |
| list_sku_costsA | List all SKU costs currently configured for profitability calculations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct domain aspect (costs, orders, order items, financial events, profitability, inventory, low stock, catalog). No two tools serve the same purpose; even similarly named tools like get_orders and get_order_items are clearly differentiated in their descriptions.
All tools use snake_case, but the verb prefix is inconsistent: list_sku_costs uses 'list' while get_orders, get_order_items, get_financial_events, and get_low_stock_alerts all use 'get' for list-returning operations. This violates the common convention that 'get' fetches a single item and 'list' fetches multiple, which could mislead an agent.
With 9 tools, the server is well-scoped for Amazon FBA operations. Each tool covers a necessary capability without redundancy, and the count falls comfortably within the ideal 3-15 range.
The surface covers the core FBA operations: order retrieval, financials, inventory levels, low stock alerts, catalog lookup, and profitability calculation. Minor gaps include lack of a delete operation for SKU costs and no tool to fetch a single order's full header details, but these are not critical.