Model Context Protocol server for retailerapi.com — unified product data across major US retailers (Walmart, Amazon, eBay, Target, Best Buy, Lowe's
Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Model Context Protocol server for retailerapi.com — unified product data across major US retailers (Walmart, Amazon, eBay, Target, Best Buy, Lowe's, Home Depot) plus universal URL passthrough for every Shopify store and any retailer that. The mcp mcp server is what makes that connection.
Model Context Protocol server for retailerapi.com — a unified product-data API covering major US retailers. Two tools your AI agent can call directly: product lookups and live offers.
The server ships on npm as @retailerapi/mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Cursor — Add to ~/.cursor/mcp.json (or the project-level .cursor/mcp.json):lookup_product — Resolve any identifier (UPC / EAN / ISBN / GTIN / Amazon ASIN / retailer item_id) into a normalized product summary. Base call (1 token) returnsget_offers — List current marketplace sellers on a product, including price, in-stock state, and which seller owns the buy boxConfiguration is passed through the environment: RETAILERAPI_KEY, RETAILERAPI_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Cursor, lookup_product, get_offers — is a fair guide to whether it matches your workflow. It is maintained by retailerapi; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Cursor | Add to ~/.cursor/mcp.json (or the project-level .cursor/mcp.json): |
| lookup_product | Resolve any identifier (UPC / EAN / ISBN / GTIN / Amazon ASIN / retailer item_id) into a normalized product summary. **Base call (1 token)** returns: title, brand, image, current price, identifiers, weight, dimensions, M |
| get_offers | List current marketplace sellers on a product, including price, in-stock state, and which seller owns the buy box. |
{
"mcpServers": {
"retailerapi": {
"command": "npx",
"args": ["-y", "@retailerapi/mcp"],
"env": {
"RETAILERAPI_KEY": "rk_live_your_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| RETAILERAPI_KEY | Credential the server authenticates with. | Yes |
| RETAILERAPI_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.