walmart

The Walmart MCP Server exposes tools to access Walmart Affiliate data and related Walmart APIs through the Model Context Protocol (MCP). It enables AI agents to perform advanced product searches, retrieve detailed product information, analyze customer reviews, locate nearby Walmart stores, and explore trends and taxonomy, all from within MCP-enabled clients like Claude Desktop or Gemini CLI. Use the provided Walmart tools (e.g., walmart_search, walmart_product_lookup, walmart_reviews, walmart_stores, walmart_feeds, walmart_taxonomy, walmart_recommendations) to build conversational flows that fetch live Walmart data and return structured, human-readable responses suitable for chat interfaces. The server operates as an MCP-compliant endpoint; you can run it locally in Stdio mode or expose it over HTTP/SSE for remote usage. To get started, configure your MCP client with the Walmart server entry and provide your required credentials so the server can authenticate with the Walmart Affiliate API when needed.

Prerequisites:

• Node.js (LTS) and npm installed on your machine
• Access to a MCP client configuration (Claude Desktop, Gemini CLI, etc.)

Installation steps:

1. Install Node.js from https://nodejs.org/ if you haven’t already.
2. Open a terminal and verify installations:
   • node -v
   • npm -v
3. Run the Walmart MCP server via npx (no local package install required): npx -y walmart-mcp@latest
4. Alternatively, if you prefer to pin a specific version, replace latest with a version tag, e.g., walmart-mcp@1.2.3: npx -y walmart-mcp@1.2.3
5. In your MCP client configuration (e.g., claude_desktop_config.json), add the Walmart server entry as shown in the example, including environment variables for credentials if needed.
6. Ensure your environment variables are set before starting the MCP client and point the client to the Walmart MCP endpoint.

Tips and caveats:

• The Walmart MCP credentials (WALMART_MCP_LICENSE_KEY and optional Walmart Affiliate keys) can be configured in the client config under the Walmart entry. If Walmart credentials are not provided, the server will fall back to built-in defaults where available.
• For remote HTTP/SSE mode, you can run the server with command-line flags to enable SSE and specify a port (e.g., npx walmart-mcp@latest --sse --port 3000) and then point your MCP client to http://localhost:3000/mcp.
• The available tools map to specific Walmart API functionalities: walmart_search for catalog search, walmart_product_lookup for item details, walmart_reviews for sentiment and review summaries, walmart_stores for geolocation, walmart_feeds for trends/bestsellers, walmart_taxonomy for category navigation, and walmart_recommendations for related items.
• If you encounter authentication issues, ensure your WALMART_MCP_LICENSE_KEY is valid and that optional Walmart credentials (CONSUMER_ID, PRIVATE_KEY, KEY_VERSION, PUBLISHER_ID) are correctly provided if your workflow requires them.
• The server is designed to work with MCP-compliant hosts; ensure your client supports JSON-RPC 2.0 requests and SSE if using the remote mode.