Apex MCP server reference

High-level counts for the seller's Apex account: ASINs in their product database, how many are profitable, how many profitable ones they already sell versus not yet, supplier count and plan. Call this first for general questions about how the business is doing.

No arguments.

Profitable ASINs in the seller's database that they are NOT currently selling, best profit first. Use for 'what should I source next' or 'what am I missing'.

Profitable products the seller already sells that are lowest on stock. Use for 'what should I reorder' or 'what is running out'.

Structural gaps holding the seller back: empty database, no or few suppliers, untapped profitable ASINs, lower plan. Use before suggesting what to work on next.

No arguments.

Monthly profit and loss from Amazon sales for the last N months: sales, units, refunds, fees, cost of goods and gross profit per month. Use for 'how did I do in August' or 'is profit trending up'.

Profit and loss statement over a date range, bucketed by day, week or month (Sellerboard-style). Dates are YYYY-MM-DD. Defaults to the last 12 months by month. A range by day may cover at most about three months, by week about two years.

Search the seller's product database (Apex Blue Databases): every ASIN they have sourced with cost, Buy Box price, profit, ROI, margin, stock and rank. Search matches ASIN, UPC, supplier SKU and title. Leave search empty to page through everything. Sort with orderBy like 'grossBuyBox:DESC' or 'roi:DESC'.

Catalog scans the seller has run through the UPC Scanner (Apex Green): one row per uploaded supplier catalog with its name, supplier, when it ran, line count and how many products it found, newest first. Pass vendorId (the supplier's id from get_purchase_orders' vendor.id or the Apex suppliers list) to see only that supplier's scans. Use the scan id with get_catalog_scan_results. For 'which profitable products does this supplier have that I do not have yet': call this with the supplier, take the latest scan id, then call get_catalog_scan_results with onlyNew=true and orderBy='profit:DESC'.

Products found in one catalog scan with cost, Amazon price, profit, ROI, margin, rank and seller counts. Search matches title, brand, ASIN or UPC. Sort with orderBy like 'profit:DESC' or 'roi:DESC'. Every row has inDatabase: true when the seller already holds that ASIN as an active product in their database. Set onlyNew=true to return only products NOT yet in their database (total then counts just those). That, with orderBy='profit:DESC', answers 'which profitable products does this supplier have that I do not have yet': find the scan with list_catalog_scans, then call this.

The seller's purchase orders (Apex Blue Purchase Orders page): vendor, order date, status, number of lines, units, total landed cost, projected revenue, profit, ROI and margin, destination warehouse, expected arrival. status='open' (default) is the page's Open tab: orders still being built, not yet submitted (status 'draft'). status='all' adds the Closed tab: submitted orders, each 'submitted' (sent, no shipment yet), 'in_transit' (inbound shipment created, not arrived) or 'received' (arrived). Projections use the Buy Box price, or the line's target price where one is set, minus fees and landed cost. Search matches vendor name, ASIN or product title. Newest first.

The seller's live Amazon listings as the repricer (Apex Gold) sees them: your price, Buy Box price, lowest offer, stock, 7 and 30 day units, fees, break-even and the strategy applied. Search matches SKU, ASIN or title.

What the repricer has been worth: units and revenue within seven days of a price it changed and Amazon accepted, with margin before and after.

No arguments.

Minimum advertised price (MAP) status by brand. Without a brand: one row per brand with how many active listings it has and how many have MAP enforcement on. With a brand: that brand's listings with MAP price, whether enforcement is on, and the current listing price.

FBA inventory per SKU with available, reserved and inbound units, sales velocity, days of inventory, stock status (Out of Stock, Restock, Enough Stock, Overstock), recommended restock and aged units. view='aging' narrows to SKUs with units past the aging line. Sort by any column, e.g. sortKey='daysOfInventory'.

Find brands to source from (Apex Green Brands): one row per brand with how many products Amazon lists for it, average price, average sellers per listing, share sold by Amazon, rating and average sales rank. search matches the brand name; category narrows to a department such as 'Health & Household'. Leave search empty to browse (free). Naming a brand counts toward the plan's monthly brand-search allowance exactly as typing it in the app does (a brand already looked at this month costs nothing again), and an empty search costs nothing. The sourcing loop: search_brands to pick a brand, research_products with that brand and inMyDatabase='hide' to find what is not yet in the seller's database, then add_products_to_database or create_draft_purchase_order (write links only).

Search Amazon products the way the Apex Products page does (Apex Green): ASIN, title, brand, price, sales rank, estimated monthly sales, number of sellers, whether Amazon sells it, estimated net proceeds after fees, and inDatabase (true when the seller already holds it as an active product). Give a brand (from search_brands) for the best results; browsing everything is slow and arbitrary. Set inMyDatabase='hide' to see only products the seller does not already have, which is the right setting before adding anything. soldByAmazon='no' leaves out products Amazon sells itself. orderBy is a column and direction such as 'salesRank:ASC', 'price:DESC', 'sellersCount:ASC' or 'estimatedMonthlySales:DESC'. Next steps for a good product: add_products_to_database or create_draft_purchase_order (write links only; they need the seller's cost from the supplier).

Create a DRAFT purchase order for one supplier in the seller's Apex Blue Purchase Orders page (it appears on the Open tab). It is never submitted: the seller reviews and submits it in Apex. Give the supplier (id or name) and lines of {asin, quantity, unitCost?}. An ASIN already in the database under that supplier uses its cost unless you give unitCost (then only this order's line cost is set, the database is untouched); an ASIN that is not there needs unitCost and is added to the database as a draft product. Destination and notes are chosen in Apex when the order is submitted, not here. Pass a requestId so a retry cannot make a second order. Ask the seller for costs and quantities; never invent them.

Add products to the seller's Apex Blue database as DRAFTS (the Drafts tab of the Databases page), exactly like uploading the bulk-upload template. Each item is {asin, unitCost, vendor?, casePack?, vendorSku?}: unitCost is the seller's cost per unit from the supplier, never a guess; every product needs a supplier, given per item or once as the top-level vendor (a name or id; it must already exist, see add_vendor); casePack defaults to 1. A product already in the database is skipped and reported, never duplicated. Nothing is made active: the seller reviews the drafts in Apex.

Add a supplier to the seller's Apex Blue Vendors page, the way its Add vendor form does (it starts as a lead on the pipeline board). Name is required; website and email are optional. If a supplier with that name already exists nothing is created and the existing one is returned. Apex suppliers have no notes field, so put anything else in the conversation, not here.