Competitor Price Stock Changelog Monitor MCP server

Competitor Price, Stock, and Changelog Monitor MCP Server

An MCP server for the Mamba Labs Competitor Price, Stock, and Changelog Monitor actor on Apify. Give it competitor sites. Each run compares every site with the state saved by the last run and returns only what changed.

What's Inside

• What it does
• Quick start
• Prerequisites
• Example prompts
• Tool
• Inputs
• Pricing
• Your keys
• Full actor documentation
• License

What it does

• Stores: Shopify stores through their public product feed and WooCommerce stores through their public Store API. Changes: pricechange, compareatpricechange, outofstock, backinstock, newproduct, removedproduct, each with the product, variant, old and new value, and a link.
• SaaS sites: the pricing page and changelog the site links to. Changes: planadded, planremoved, planpricechange, pricingpagechange, and changelog_entry.
• One row per site per run: sitebaseline on the first check under a statekey, then sitecheck with changesfound for a site that changed, or a free no_change row when nothing moved.

Unreadable sites come back free with a row_status saying so.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claudedesktopconfig.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-competitor-price-stock-changelog-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-competitor-price-stock-changelog-monitor"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The monitorcompetitorchanges tool appears.

Prerequisites

• Node.js 18 or newer.
• An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.

Example prompts

Shortened. The full README is on GitHub.