Skip to main content
Glama
bigl34

inFlow Inventory MCP Server

by bigl34
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to inFlow Inventory MCP Server

No user-submitted related servers found.

    Related Servers

    • ECOUNT MCP Server

      storehausai
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with ECOUNT ERP through natural language, providing tools for products, inventory, sales, purchases, and more.
      23
      8 npm
      3
      MIT

    • Skulabs MCP Server

      tindevelopers
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to interact with Skulabs inventory management system through comprehensive tools for managing products, orders, customers, and analytics. Supports voice agents like Retell AI and desktop applications like Claude for natural language inventory operations.
      -

    • Fabriqo MCP Server

      usefabriqo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing workspace products, inventory, orders, manufacturing, and traceability through natural language in AI assistants like ChatGPT, Codex, and Claude.
      28 npm
      MIT

    • InventoryApplication MCP

      privastx
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and modify inventory data through natural language, bridging AI assistants to the inventory management system without requiring SQL knowledge or direct database access.
      -

    • SkuVault MCP Server

      dbankscard
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with the SkuVault inventory management system API for product management, inventory control, warehouse operations, and analytics through natural language.
      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

    C2.6/5.0

    Scored across 86 tools

    Disambiguation2/5

    With 86 tools, many overlap: upsert_* and set_* pairs exist for most entities, multiple serial-lookup tools (search_serial_number, list_serial_numbers, get_product_serials, list_all_serials), and receipt tools overlap with purchase-order updates. An agent must parse long descriptions to distinguish legacy vs preview-first replacements, and some boundaries remain unclear.

    Naming Consistency5/5

    Names consistently use snake_case verb_noun conventions (list_products, get_sales_order, set_webhook), with predictable prefixes for list/get/upsert/set/delete/remove. Minor legacy vs newer 'set' verbs coexist but the pattern is stable.

    Tool Count1/5

    86 tools is far beyond a well-scoped set; the server includes many deprecated legacy writes plus preview-only replacements that cannot yet apply, inflating the surface. This is an extreme mismatch for an inventory MCP and will burden tool selection.

    Completeness2/5

    Core transaction types have create/read/update paths, but many admin/lookup entities (locations, categories, pricing schemes, payment terms, tax codes, currencies, custom fields, team members) are list-only with no create/update/delete. Also many set_* write tools are preview-only and apply remains unavailable, leaving significant gaps for full lifecycle operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources