Traject Ecommerce

What the Traject Ecommerce MCP server does

The Traject Ecommerce MCP server gives MCP-compatible agents access to selected Amazon and Walmart catalog and review data. Amazon operations use the Rainforest API and identify products with ASINs. Walmart operations use the BlueCart API and identify products with item IDs.

The server covers three operation types for each marketplace:

• Search products by keyword.
• Retrieve details for a known product.
• Retrieve customer reviews for a known product.

Amazon product results include fields such as title, brand, price, rating, ratings total, bestsellers rank, and image. Walmart product results include title, brand, price, rating, ratings total, and image. Review responses include review text, rating, date, and verified-purchase status; Amazon reviews also include helpful-vote counts.

How it works

A client can connect to the hosted MCP endpoint at https://gateway.pipeworx.io/traject-ecommerce/mcp. The scoped endpoint lists this pack's tools and also exposes shared Pipeworx meta-tools. Those meta-tools can route broader requests through the gateway, while the direct tools remain limited to the Amazon and Walmart capabilities described here.

The same gateway also provides a full endpoint at https://gateway.pipeworx.io/mcp. The full endpoint lists tools from the wider Pipeworx catalog directly. Either gateway connection requires the marketplace API key when calling the relevant tool; the server does not supply those keys.

The Traject Ecommerce MCP server can also run locally through the npm package @pipeworx/mcp-traject-ecommerce. In local mode it communicates over standard input and output and exposes only this pack's six tools, without the gateway's shared meta-tools.

Setup and configuration

For a hosted connection, add the scoped URL as an MCP server in a compatible client. A local stdio configuration can use npx with the package name and the -y option:

{
  "mcpServers": {
    "traject-ecommerce": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-traject-ecommerce"]
    }
  }
}

Start the package directly with npx -y @pipeworx/mcp-traject-ecommerce to verify that it launches. No environment variables are specified. Instead, provide a Rainforest key through the _apiKey argument for Amazon tools and a BlueCart key through _apiKey for Walmart tools. Amazon search and product or review calls also accept an amazon_domain value, such as amazon.com.

Tools and capabilities

The six direct tools are:

• amazon_search: searches Amazon by search_term and returns position, title, ASIN, price, rating, and ratings total.
• amazon_product: retrieves Amazon details using an ASIN.
• amazon_reviews: retrieves Amazon reviews using an ASIN, including helpful votes.
• walmart_search: searches Walmart by search_term and returns position, title, item ID, price, rating, and ratings total.
• walmart_product: retrieves Walmart details using an item ID.
• walmart_reviews: retrieves Walmart reviews using an item ID.

The Traject Ecommerce MCP server is suited to product lookup, marketplace comparisons, review collection, and agent workflows that need structured shopping data rather than browser interaction. It does not document purchase, cart, inventory, seller-management, or order-management tools.

Limitations and notes

Marketplace coverage depends on the two upstream services: Rainforest for Amazon and BlueCart for Walmart. The supplied material documents API-key arguments but does not specify rate limits, response pagination, regional coverage beyond the amazon_domain argument, or how review results are ordered.

The hosted pack endpoint includes additional shared gateway schemas, so its reported tool count is larger than the six direct tools. The local package does not include those shared tools or ask_pipeworx routing. Use the hosted endpoint when gateway-wide discovery is useful; use the local package when a standalone stdio connection is preferred.