Skip to main content
Glama

Related Servers

Alternatives to ThriveCart MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query and manage ThriveCart data across multiple accounts, including products, offers, transactions, revenue, customers, subscriptions, and affiliates, while keeping accounts separate.
      24
      22 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT, Claude, and other AI agents to draft estimates, schedule jobs, assign crew members, and review receivables in a user's signed-in business account, requiring approval before actions reach other people.
      7
      Elastic 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects a signed-in InvoiceASAP account to ChatGPT, Claude and other AI agents so they can review unpaid invoices, customer balances and aging, sales reports by item or representative, and job photos. Actions that change data, such as marking an invoice paid or altering payment settings, wait for the user's approval.
      Elastic 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT, Claude, and other AI agents to access a signed-in restaurant POS account for sales reporting, flagged-bill review, inventory reads, menu management, and approval-gated write actions.
      7
      Elastic 2.0

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are clearly distinct: open/read/click/type/close map to distinct browser actions. thrivecart_guide and thrivecart_status are somewhat close as onboarding/readiness helpers, but the descriptions make their roles separable.

    Naming Consistency5/5

    All tool names use a consistent thrivecart_ prefix followed by a short snake_case action verb. The pattern is predictable across the entire set.

    Tool Count5/5

    Seven tools is well-scoped for a browser-automation server: setup, page reading, interaction, and cleanup are each represented without excess. Each tool appears to earn its place.

    Completeness4/5

    The surface covers the core browser lifecycle: guide, status check, open session, read page, click, type, and close. Minor gaps like explicit scrolling or waiting could be worked around via clicking/reading, but are not directly exposed.