Skip to main content
Glama

@replenishradar/mcp-server

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

Setup

  1. Get your API key from ReplenishRadar > Settings > API Keys.

  2. Add this server to your MCP client config. In Claude Desktop, open Settings > Developer > Edit Config:

{
  "mcpServers": {
    "replenishradar": {
      "command": "npx",
      "args": ["-y", "@replenishradar/mcp-server"],
      "env": {
        "REPLENISHRADAR_API_KEY": "rr_sk_your_key_here"
      }
    }
  }
}
  1. 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:

POST https://api.replenishradar.com/api/public/agent-intake

Related MCP server: shopico

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

Available Tools

16 tools
rr_create_locationB

Create a manual inventory location such as warehouse, 3PL, or inbound location.

Inputs: name (required), type (required), city, state, +4 more.

rr_delete_agent_contextA

Delete one agent context entry by namespace and key. Records actor provenance. The namespace must be granted to this key.

Inputs: key (required), namespace (required).

rr_execute_replenishment_actionA

Execute a replenishment action in draft mode: creates a draft purchase order and/or draft transfer order for the action's items. Idempotent by idempotency_key; rejects with conflict if the action changed since prepare (stale expected_updated_at) or if the same key is reused with a different payload or actor. Never auto-sends to suppliers and never commits stock.

Inputs: action_id (required), idempotency_key (required), expected_updated_at (required).

rr_get_agent_contextA

Get one agent context entry by namespace and key. Expired entries are omitted. The namespace must be granted to this API key by a human admin.

Inputs: key (required), namespace (required).

rr_get_demand_forecastB

Get demand forecast statistics (mu/sigma) for a SKU or item. Returns active forecast windows.

Inputs: sku, item_id, store_id, window_days.

rr_get_document_upload_urlC

Create a document record for a purchase order (invoice, packing slip, etc.). Requires Scale tier.

Inputs: po_id (required), filename (required), description, document_type.

rr_get_purchase_orderA

Get a single purchase order with full details including line items and vendor info.

Inputs: po_id (required).

rr_list_agent_contextA

List live agent context entries for a single namespace. The namespace is required and the limit is bounded (max 200). This tool never lists across namespaces.

Inputs: namespace (required), limit, key_prefix.

rr_list_purchase_ordersB

List purchase orders with filtering by status, vendor, and search. Supports pagination.

Inputs: limit, offset, search, status, +1 more.

rr_list_suppliersA

List all suppliers/vendors for the organization. Optionally include vendor SKU mappings.

Inputs: include_skus.

rr_prepare_replenishment_actionA

Preview a replenishment action and return its current updated_at before executing. Use the returned updated_at as expected_updated_at on execute/resolve/retry.

Inputs: action_id (required).

rr_record_pi_reviewB

Record proforma invoice details on a purchase order (PI number, date, total, terms).

Inputs: po_id (required), pi_date, pi_terms, pi_total, +1 more.

rr_resolve_replenishment_actionA

Resolve a replenishment action as no-action with a reason. Idempotent; requires idempotency_key and expected_updated_at and applies the same stale-state conflict contract as execute.

Inputs: reason (required), action_id (required), idempotency_key (required), expected_updated_at (required).

rr_retry_replenishment_actionA

Retry a blocked or failed replenishment action by re-running the draft execution path. Idempotent; requires idempotency_key and expected_updated_at and applies the same stale-state conflict contract as execute.

Inputs: action_id (required), idempotency_key (required), expected_updated_at (required).

rr_set_agent_contextA

Store a bounded JSON object under a namespace and key. The value must be a JSON object (max 16 KiB), must not contain secrets or raw PII, and ttl_seconds is optional and capped at 90 days. The namespace must be granted to this key.

Inputs: key (required), value (required), namespace (required), scope_ref, +1 more.

rr_set_stock_at_locationC

Set stock quantity for a SKU at a manual location.

Inputs: sku (required), quantity (required), location_id, location_name.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools are clearly distinct: forecasting, suppliers, purchase orders, replenishment actions, locations, and agent context each target different resources. The only mild ambiguity is between rr_get_demand_forecast and rr_prepare_replenishment_action, since both relate to replenishment planning, but their descriptions clarify that one returns forecast statistics and the other previews an action.

    Naming Consistency4/5

    The rr_ prefix is consistent, and most tools follow a verb_noun pattern (list_suppliers, get_purchase_order, create_location, set_stock_at_location). Minor deviations exist: rr_get_demand_forecast uses a noun phrase rather than a simple verb_noun, and rr_record_pi_review uses an abbreviation, but the overall pattern is predictable.

    Tool Count4/5

    16 tools is on the higher end but still reasonable for a supply-chain/replenishment domain that spans forecasting, purchase orders, replenishment actions, locations, and agent context. Each tool serves a distinct function, though the agent-context tools (5 tools) could arguably be a separate server.

    Completeness4/5

    The core replenishment workflow is well covered: forecast, prepare, execute, resolve, retry, and purchase order read/list. Minor gaps include no update/delete for purchase orders and no supplier creation/update, but these are likely outside the server's purpose. The agent-context CRUD is complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language queries of retail sell-through, inventory coverage, out-of-stock risk, and reorder suggestions from POS and warehouse data, with an optional agent that emails reorder proposals.
      80 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables small shopkeepers to manage inventory conversationally, tracking daily burn rates, predicting stockouts and spoilage, generating supplier-grouped purchase orders, planning reorders under budget constraints, creating near-expiry clearance markdowns, and projecting profit margins.
      MIT