ReplenishRadar

io.github.ReplenishRadarPublished by GitHub account ReplenishRadarv1.1.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyProductivity & Workflow Data & Analytics Business & Commerce

Server details

Identifier: io.github.ReplenishRadar/MCP
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account ReplenishRadar for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.ReplenishRadar%2FMCP.svg)](https://sourceweft.com/mcp/io.github.ReplenishRadar%2FMCP?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Connects an AI assistant to ReplenishRadar for Shopify and Amazon inventory planning, forecasting, stockout risk and replenishment actions.

What you can do: Exposes roughly 50 tools over stdio for live inventory data: stockout risk, inventory position by location, demand forecasts, suggested purchase orders, replenishment actions, alerts, suppliers, purchase orders, sales history, top sellers, slow movers, inventory value and SKU or store health. It also offers basic writes such as acknowledging alerts, adding PO notes, requesting approval and preparing or executing replenishment actions, plus sensitive writes like creating, updating, sending or cancelling purchase orders and setting stock at manual locations. A small org-scoped key/value context store lets an agent remember bounded workflow state.
When to use it: Use it when an assistant should answer questions about stockout risk, demand forecasts, purchase orders or replenishment for a ReplenishRadar account, or drive draft purchase orders and replenishment actions from that data. It suits buyers and operations teams already running ReplenishRadar on Shopify or Amazon.
Requirements: Local Node.js runtime via npx package @replenishradar/mcp-server, desktop MCP client such as Claude Desktop. Requires a ReplenishRadar API key in REPLENISHRADAR_API_KEY (rr_sk_ prefix); REPLENISHRADAR_API_URL is optional and defaults to the vendor API. A paid tier governs available tools and rate limits.

Before you install

The API key is a secret and grants access to inventory and purchasing data. Sensitive write tools can create, send or cancel purchase orders and change stock; autonomous execution sends POs or commits transfers when the key has sensitive_write, the operation tool group and an enabled budget, so review budgets and allowlists first. Draft mode is the default. Agent context writes reject secrets and raw PII, and namespaces need per-key admin allowlisting.

Installation

In SourceWeft

Open ReplenishRadar in the dashboard and add it to a workspace.
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

@replenishradar/mcp-server

[smithery badge]

Connect AI agents to live ReplenishRadar inventory data. Works with Claude Desktop, OpenClaw, and any MCP-compatible client.

Setup

Get your API key from ReplenishRadar > Settings > API Keys.
Add this server to your MCP client config. In Claude Desktop, open Settings > Developer > Edit Config:

json

{  "mcpServers": {    "replenishradar": {      "command": "npx",      "args": ["-y", "@replenishradar/mcp-server"],      "env": {        "REPLENISHRADAR_API_KEY": "rr_sk_your_key_here"      }    }  }}

{  "mcpServers": {    "replenishradar": {      "command": "npx",      "args": ["-y", "@replenishradar/mcp-server"],      "env": {        "REPLENISHRADAR_API_KEY": "rr_sk_your_key_here"      }    }  }}

Restart Claude Desktop and ask: "What are my top stockout risks?"

No ReplenishRadar account yet? Use the public agent intake endpoint to request a short-lived, read-only sandbox key before configuring the server:

Available Tools

Read

Standard includes limited read API access. Growth adds diagnosis/status read tools.

Tool	Description
`rr_get_stockout_risk`	Stockout risk levels for SKUs
`rr_get_inventory_position`	Stock-by-location for an item
`rr_get_demand_forecast`	Demand forecast stats
`rr_get_suggested_purchase_orders`	Suggested POs
`rr_get_replenishment_actions`	Canonical buyer replenishment actions
`rr_get_replenishment_action`	One replenishment action with event history
`rr_get_alerts`	Active alerts
`rr_list_items`	List inventory items
`rr_get_sync_status`	Recent sync history
`rr_list_suppliers`	List vendors/suppliers
`rr_list_purchase_orders`	List purchase orders
`rr_get_purchase_order`	Single PO with line items
`rr_get_po_pdf`	PO PDF info
`rr_get_po_documents`	Documents attached to a PO
`rr_get_po_notes`	Notes attached to a PO
`rr_get_sales_history`	Sales history
`rr_get_top_sellers`	Top-selling SKUs
`rr_get_slow_movers`	Slow-moving SKUs
`rr_get_inventory_value`	Inventory value breakdown
`rr_get_sku_health`	SKU-level health summary
`rr_get_lost_sales`	Estimated lost sales from stockouts
`rr_get_store_health`	Store connection and sync health
`rr_get_data_freshness`	Freshness status by data dimension
`rr_get_setup_status`	Setup milestones and next step
`rr_get_recent_activity`	Recent alerts, POs, and sync rollup
`search_knowledge`	ReplenishRadar product knowledge search
`rr_evaluate_fit`	Deterministic ICP + tier fit verdict (no org data)

Basic write (Standard tier and up)

Safe, low-blast-radius writes - no money or stock mutation.

Tool	Description
`rr_acknowledge_alert`	Acknowledge an alert
`rr_add_po_note`	Add a note to a PO
`rr_request_approval`	Request human approval for a PO
`rr_add_replenishment_action_note`	Add a note to a replenishment action
`rr_dismiss_replenishment_action`	Dismiss a replenishment action
`rr_prepare_replenishment_action`	Preview an action and get its current `updated_at` before execute
`rr_execute_replenishment_action`	Execute an action. `mode="draft"` (default) creates a draft PO and/or transfer; `mode="autonomous"` also sends the PO / commits the transfer when the key has sensitive_write + the operation tool group + an enabled budget and all guardrails pass (else draft-fallback or hard-refuse). Idempotent, stale-state protected
`rr_resolve_replenishment_action`	Resolve an action as no-action with a reason; idempotent, stale-state protected
`rr_retry_replenishment_action`	Retry a blocked or failed action via the draft execution path; idempotent, stale-state protected
`rr_get_document_upload_url`	Get upload URL for a PO document
`rr_record_pi_review`	Record proforma invoice details

Sensitive write (Growth tier and up)

Money / stock mutation.

Tool	Description
`rr_trigger_sync`	Trigger inventory sync
`rr_create_purchase_order`	Create a draft PO
`rr_update_purchase_order`	Update a draft PO
`rr_send_purchase_order`	Send an approved PO
`rr_cancel_purchase_order`	Cancel a PO
`rr_create_location`	Create a manual inventory location
`rr_set_stock_at_location`	Set stock at a manual location

PO creation always starts as a draft. rr_send_purchase_order only sends a PO that was already human-approved.

Action execution has two modes. rr_execute_replenishment_action with mode="draft" (the default) creates a draft PO and/or draft transfer for an action's items and never auto-sends to a supplier or commits stock. With mode="autonomous" it additionally sends the PO or commits the transfer, but only when the key has sensitive_write + the operation's tool group + an enabled per-key budget (autonomous_enabled=true) and every guardrail passes; otherwise it leaves a draft and returns an rr_request_approval hint (draft_fallback) or refuses without mutating (hard_refuse). Call rr_prepare_replenishment_action first to get the action's current updated_at, then pass it as expected_updated_at so a stale action is rejected before any write. Pass a stable idempotency_key so a retried call replays the original result instead of double-creating artifacts or double-sending.

Agent context store

A small, org-scoped, auditable key/value memory so an agent can remember bounded workflow state. rr_get_agent_context / rr_list_agent_context are read-capability; rr_set_agent_context / rr_delete_agent_context are basic-write. All four are in the agent_context tool group.

Tool	Description
`rr_get_agent_context`	Get one entry by `namespace` + `key`; expired entries are omitted
`rr_set_agent_context`	Store a bounded JSON object under `namespace` + `key` (optional `scope_ref`, `ttl_seconds`)
`rr_list_agent_context`	List live entries for ONE `namespace` (required), bounded `limit` (max 200)
`rr_delete_agent_context`	Delete one entry by `namespace` + `key`; records actor provenance

Rules and limits:

Namespaces are code-owned and per-key allowlisted. A human admin must grant your API key read/write/delete on each namespace in Settings > API Keys. Same-organization access alone is not sufficient.
No secrets, no raw PII. Writes that look like tokens, passwords, private keys, credentials, or raw emails/phones/addresses are rejected.
value must be a JSON object (not a scalar or array), capped at 16 KiB serialized.
ttl_seconds is optional and capped at 90 days; with no TTL the entry persists while the organization exists.
rr_list_agent_context requires namespace and never lists across namespaces.
scope_ref is descriptive metadata only and is not part of uniqueness - encode per-scope entries into the key (for example supplier_rules/sku:ABC123).
Sensitive namespaces (for example sourcing_economics) additionally require the key to hold the sensitive economics read capability + tool group.

Spend budgets (admin-managed, no MCP tool)

Per-API-key spend budgets - per-PO value cap, rolling-24h daily cap, max transfer quantity delta, an autonomous_enabled flag, and vendor / destination / transfer-source (or route-pair) allowlists - constrain what an autonomous key may buy or move. They are managed only by a human admin in Settings > API Keys (a JWT-admin Settings API); there is no MCP tool to read or change a budget, and an API key cannot reach the budget routes, not even for its own caps. Budgets are consumed only by autonomous send/commit, autonomous mode is off by default, and a denied autonomous action receives only a short decision reason - never the cap amounts, the allowlists, or another key's ledger.

Rate Limits

Standard ($99/mo): 10 calls/hour, read + basic-write tools
Growth ($199/mo): 100 calls/hour, read + basic + sensitive read/write + diagnosis/status tools
Scale ($499/mo): 1,000 calls/hour, full read + write capability set

Learn More

Source: README.md at commit 3071ebf

Tools

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

Version history

v1.1.0LatestSep 16, 2026

Score

50% 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
License10 pts