Propamp MCP Server

The Propamp MCP server puts your live Amazon FBA data — profit, inventory, PPC, purchase orders, shipments — inside Claude, Codex, and any other MCP-capable AI client. You sign in once with your Propamp account. There is no API key to generate and nothing to copy.

What you can do with it

Instead of exporting a report and asking questions about the spreadsheet, you ask the question directly and the assistant pulls what it needs:

• “Show my profit breakdown for the last 30 days across all Amazon marketplaces.”
• “Which products are at risk of going out of stock in the next two weeks?”
• “Which purchase order payments are due in the next 30 days, and what is the total?”
• “What is my CPA and ROI trend for the last 3 months? Which products are losing money on ads?”
• “Reconcile my last shipment’s freight cost against the invoice in the documents.”

The assistant can also act, not just read — creating a shipment draft, updating a purchase order, or logging an expense — because the tool set includes write operations. Your client asks for approval before it calls one of those.

How it fits together

The MCP server reads the data Propamp has already synced from Seller Central. It does not talk to Amazon directly, so anything you see through MCP is the same data you see in the Propamp web app.

Your AI client  ──OAuth──▶  Propamp MCP server  ──▶  Propamp  ──▶  Amazon Seller Central
  (Claude, Codex)              mcp.propamp.ai            (already synced)

That has one practical consequence worth knowing up front: if a marketplace or a date range looks empty through MCP, check the Propamp web app first. The sync, not the connection, is usually the cause.

Start here