mcpField
J
Jungle Scout

Jungle Scout

Remote
pipeworx.ioBusiness & Marketing0Updated 2d ago

About Jungle Scout

Jungle Scout is an MCP server for Amazon sellers and market researchers querying ASIN sales estimates, product data, and keyword metrics. Results include estimated units, revenue, price, and search volume; calls require the user's own API key.

Key features

  1. 01Get ASIN sales, revenue, and price estimates
  2. 02Search products by keyword or category
  3. 03Review product rank, reviews, and rating
  4. 04Get monthly keyword search volume
  5. 05Find keywords an ASIN ranks for

Use cases

  1. 01Estimate sales performance for an Amazon product
  2. 02Find Amazon products matching a search term
  3. 03Research demand for a keyword
  4. 04Inspect keywords associated with an ASIN's rankings

MCP support

It exposes Jungle Scout sales estimation, product database, and keyword data tools to MCP clients through a Pipeworx remote endpoint or local stdio MCP server. Calls require an API key supplied by the user.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/jungle-scout/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-jungle-scout

Jungle Scout MCP — Amazon sales estimates + product database + keyword data (junglescout.com). Data that generic e-commerce / traject packs lack: per-ASIN estimated units sold, revenue, and Amazon keyword search volume.

Part of Pipeworx — an MCP gateway connecting AI agents to 1882+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
junglescout_sales_estimateHow many units does an Amazon ASIN sell — returns Jungle Scout estimated units sold, revenue, and price for a product ASIN. Example: junglescout_sales_estimate({ asin: "B08N5WRWNW", marketplace: "us", _apiKey: "KEY_NAME:API_KEY" })
junglescout_product_databaseSearch Amazon products by keyword or category — returns matching ASINs with title, brand, price, rank, estimated units sold, reviews, and rating from the Jungle Scout product database. Example: junglescout_product_database({ keyword: "yoga mat", marketplace: "us", _apiKey: "KEY_NAME:API_KEY" })
junglescout_keyword_dataAmazon keyword search volume — returns monthly search volume and keyword metrics for a keyword, or the top keywords an ASIN ranks for. Pass keyword OR asin. Example: junglescout_keyword_data({ keyword: "yoga mat", marketplace: "us", _apiKey: "KEY_NAME:API_KEY" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "jungle-scout": {
      "url": "https://gateway.pipeworx.io/jungle-scout/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/jungle-scout/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1882+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/junglescout_sales_estimate. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

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

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-jungle-scout

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Jungle Scout data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.