Skip to main content
Glama
jams24

InventPay MCP Server

by jams24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to InventPay MCP Server

No user-submitted related servers found.

    Related Servers

    • Shopify Agentic MCP Gateway

      kuro-tomo
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to autonomously browse inventory, negotiate terms, manage carts, and execute secure payments on Shopify stores using standardized protocols. It provides a bridge for LLMs to handle the entire commerce lifecycle from discovery to order tracking through a verifiable mandate chain.
      5
      2
      MIT

    • wata-mcp

      votsie
      A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to manage merchant accounts, process payments, handle wallets and payouts, and sell digital goods through the wata.pro payment system.
      90
      MIT

    • miel-ruben MCP Server

      SIRGPrice
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage an online store for honey and beekeeping products, including order tracking, inventory updates, sales stats, and invoice resending via the Model Context Protocol.
      -
    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

    A3.8/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target distinct resources and actions. Slight overlap exists between get_store and get_store_analytics (both show order/product counts) and between create_payment and create_invoice, but descriptions clarify their different use cases.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: get, create, update, delete, list, add. Resources are singular for single-item operations and plural for list operations, with only minor naming variance like get_key_pool_stats.

    Tool Count4/5

    With 20 tools, the count is higher than the ideal 3-15 range but appropriate for the broad merchant platform scope covering stores, products, keys, payments, withdrawals, orders, and analytics. Each tool has a distinct purpose, so it does not feel bloated.

    Completeness4/5

    The tool surface covers core lifecycle operations for stores, products, keys, payments, withdrawals, and orders. Minor gaps exist (e.g., no store deletion, no key revocation, no payment cancellation), but these are typically not required for merchant operations and can be worked around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources