Skip to main content
Glama
ReplenishRadar

replenishradar

by ReplenishRadar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to replenishradar

No user-submitted related servers found.

    Related Servers

    • retail-mcp

      Trapa-Eureka
      A
      license
      Not graded
      quality
      A
      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.
      293 npm
      MIT

    • AMZ Vault

      TheBurdz
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects Amazon Seller Central and Amazon Advertising to any MCP client, with a settlement-accurate P&L underneath: every fee, refund and reimbursement as Amazon actually posted it, so contribution margin and breakeven are per product, per marketplace, per day. 107 tools spanning P&L, full Sponsored Products/Brands/Display management, Search Query Performance and Brand Analytics, inventory and for
      1
      MIT

    • Shopify Partner Agent

      rushikeshmore
      A
      license
      A
      quality
      F
      maintenance
      Free, open-source MCP server that connects Claude to the Shopify Partner API. 25 tools for revenue analytics, churn analysis, retention cohorts, merchant health scoring, conversion funnels, revenue forecasting, and growth velocity.
      25
      13
      MIT

    • cerebrochain-mcp-server

      CerebroChain
      A
      license
      A
      quality
      D
      maintenance
      The first logistics/WMS MCP server for AI agents. Rate shopping, inventory management, order tracking, fleet logistics, AI-powered route optimization, demand forecasting, and supply chain analytics. 18 tools across 3 tiers.
      20
      6 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources