Walmart Marketplace MCP server for your AI

In Seller Center, go to Developer Portal → API Key Management and create an API key once. The connect form asks for the Client ID and Client Secret from that key, plus an Environment value, with Auth type optional. PopMCP exchanges the pair server-side for a short-lived token and refreshes it automatically, so you never handle a token yourself.

Yes. Set Environment to Sandbox and paste a sandbox key to rehearse order acknowledgment, price pushes or inventory updates before anything touches live listings, or set it to Production for a live seller account. Either way the connection is locked to the seller account behind the key you connected.

The connection covers 137 operations across 18 Marketplace API modules: 80 reads and 57 writes. 35 load into your AI client by default and the rest stay searchable, so a question about repricer strategies or WFS rate quotes can still reach them without bloating the tool list. The largest modules are WFS, Settings and Rules.

Yes — cancel_order_lines, refund_order_lines, issue_refund and retire_an_item are all in the write set, alongside update_price and update_inventory. Set the connection to read-only if the agent should only report, or keep full access with approval required for writes so anything that moves money or takes an offer off the site waits for your sign-off. Reads like get_all_orders and get_returns are unaffected either way.

WFS is the largest module in the connection at 22 operations. An agent can convert items for WFS, create and confirm carrier rate quotes, cancel an inbound shipment and cancel a customer order. Triggers also fire when a new inbound shipment is created and when units move in or out of your WFS stock.

Walmart cancels an order line on its own when it isn't shipped in time, and there is a webhook trigger for exactly that event so you find out immediately. The better pattern is to work off the Order ready to ship trigger, which fires once an order is released and waiting to be acknowledged, then have the agent run acknowledge_orders and ship_order_lines. get_lag_time tells you the ship window you are working against.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 137 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 35-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

A tool is something your AI calls — there are 137 here. A trigger is something PopMCP watches for you: 18 Walmart Marketplace events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Walmart Marketplace.