ReplenishRadar

io.github.Limited-HorizonPublished by GitHub account Limited-Horizonv1.0.6Updated Oct 24, 2026

Shopify + Amazon inventory planning, forecasting & replenishment over MCP (49 tools).

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Local MCP server exposing ReplenishRadar's Shopify and Amazon inventory planning, forecasting and replenishment tools to an AI assistant.

What you can do
  • Plan inventory across Shopify and Amazon sales channels
  • Forecast demand and plan replenishment through the server's 49 tools
  • Work with ReplenishRadar data using an API key tied to the account
  • The manifest lists no individual tools, so exact capabilities are not documented here
When to use it
Useful when you sell on Shopify and/or Amazon and want an assistant to help with demand forecasting, stock planning and replenishment decisions inside ReplenishRadar, rather than switching to its dashboard.
Requirements
Runs as a local stdio process installed from the npm package @replenishradar/mcp-server (Node.js). Requires a ReplenishRadar API key in REPLENISHRADAR_API_KEY, with the rr_sk_ prefix. Optionally set REPLENISHRADAR_API_URL; it defaults to the ReplenishRadar API endpoint. Desktop client only; not web-executable.
Before you install
The API key is a secret granting access to your ReplenishRadar account data; keep it out of shared configs and logs. The server acts on live inventory and sales-channel data, so review any changes it proposes before applying them. Requests go to ReplenishRadar's API, which receives your inventory and sales data.

Installation

In SourceWeft

  1. Open ReplenishRadar in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.6LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.