The same RSA signing dance, every time
Every team selling on Walmart Marketplace writes the same RSA-signing glue — load PEM, build canonical string, sign, base64, attach four headers, generate a fresh correlation ID, time it to epoch ms, retry on 5xx, paginate. None of it is hard. All of it is annoying.
This package is the assembled, tested version. It exposes seven read-only Walmart Marketplace endpoints as MCP tools, with the signing and pagination handled for you. Add three env vars to your MCP client config and you're done.
The seven read-only tools
walmart_search_products— by query, page, page_sizewalmart_get_product— full item detail by SKUwalmart_search_orders— date range, status filterwalmart_get_order— full purchase order detailwalmart_get_inventory— qty on hand by SKUwalmart_get_pricing— current price + strikethroughwalmart_get_settlement_report— fetch by report id
Every tool returns the standard JSON envelope. Auth signing uses
RSA-2048 with SHA-256 (PKCS#1 v1.5 padding) per Walmart's public docs.
Cryptography is handled by the audited cryptography
library — the only added runtime dep over mcp + requests.
61 unit tests cover signature verification, retry behavior, and the
tool layer.
Who this is for
This MCP server is for you if:
- You sell on Walmart Marketplace and want Claude (or any MCP client) to be able to answer questions about your catalog, orders, and settlement reports without you writing glue.
- You'd rather configure three env vars than maintain an internal Walmart client library.
It's not for you if:
- You don't sell on Walmart Marketplace.
- You need feeds / write operations. v0.1 is read-only by design.