CartScout MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | Your RapidAPI key (from RapidAPI dashboard). Required for using the API unless CARTSCOUT_API_URL and CARTSCOUT_API_KEY are provided. | |
| CARTSCOUT_API_KEY | No | API key when using a directly issued CartScout key instead of RapidAPI. Must be used together with CARTSCOUT_API_URL. | |
| CARTSCOUT_API_URL | No | API URL when using a directly issued CartScout key instead of RapidAPI. Must be used together with CARTSCOUT_API_KEY. | |
| CARTSCOUT_RAPIDAPI_HOST | No | RapidAPI host of the API. | cartscout-api.p.rapidapi.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_productA | Get the live price, stock status, discount, variants, identifiers (SKU, GTIN) and rating of one product page. Works with Shopify, WooCommerce, Walmart and eBay stores, Amazon in beta. Uses 1 extraction from the user's CartScout plan. |
| compare_productsA | Compare 2-10 product pages side by side: cheapest, cheapest in stock, best rated, biggest discount, price spread and whether every page sells the same product (matching GTIN). Uses 1 extraction per URL and needs a paid CartScout plan (PRO or higher). |
| check_dealA | Rate whether a product's current price is a good deal compared with its recorded price history, with the average, lowest and highest price in the period. History builds up each time CartScout reads the product, so a product seen for the first time has little to compare against. |
| get_price_historyA | Recorded price and stock changes of a product page, with the current, lowest and highest price. History exists only for products CartScout has read before; call get_product first to start it. Does not use extractions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clear, distinct operation: one product snapshot, multi-product comparison, deal rating, and historical data. While check_deal and get_price_history both use history, check_deal provides a computed verdict while get_price_history returns raw data, so there is no real ambiguity.
All tool names follow a consistent verb_noun pattern with lowercase snake_case: get_product, compare_products, check_deal, get_price_history. The verb choice clearly conveys the action and the object is always the resource involved.
Four tools is an appropriately tight scope for a price-tracking and product-research server. Each tool covers a distinct core need—single product lookup, comparison, deal assessment, and history—without redundancy or bloat.
The core product research and price history lifecycle is covered well, including starting history via get_product. Minor gaps exist such as no search/discovery tool or watchlist/alerts, but the available tools support the main workflows without dead ends.