Skip to main content
Glama
aleccritser

storelink-mcp

by aleccritser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to storelink-mcp

No user-submitted related servers found.

    Related Servers

    • korral-storelink-mcp

      Ricoledan
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables Duvo agents to perform Korral category buyer tasks against the StoreLink API, including checking stock risk, reviewing sales, and raising replenishment orders.
      5
      MIT

    • korral-mcp

      ilyadurov97
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets a Duvo agent talk to Korral's StoreLink API, enabling category buyers to offload daily stock checking, replenishment ordering, and order tracking tasks.
      -

    • storelink-mcp

      jaredalonzo
      F
      license
      A
      quality
      B
      maintenance
      MCP server for managing store replenishment, including listing stores, raising orders, checking order status, and viewing SKU reports with observability and key rotation handling.
      4
      -

    • mcp-netsuite-practice

      awnt9
      F
      license
      A
      quality
      B
      maintenance
      MCP server that exposes read-only NetSuite tools for querying warehouse stock levels and order status, using mock data locally and a pluggable client interface.
      2
      -

    • erp-billing

      757607106
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI platforms to search products, customers, and warehouses, and prepare and submit sales orders to a fixed ERP endpoint with per-session bearer authentication.
      -
    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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: listing stores, getting store details, checking inventory/POS, creating a replenishment, and retrieving a replenishment. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_stores, get_store, get_on_hand_vs_pos, create_replenishment, get_replenishment). The naming is predictable and clear, with the compound 'get_on_hand_vs_pos' still fitting the convention.

    Tool Count5/5

    The server has 5 tools, which is well-scoped for its purpose of store and replenishment management. Each tool serves a necessary function without redundancy, making the set neither too thin nor too heavy.

    Completeness4/5

    The main workflow is covered: list/get stores, check inventory vs POS, create a replenishment, and check its status. A minor gap is the lack of a 'list_replenishments' tool or update/cancel capabilities, but the core lifecycle is functional.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources