Skip to main content
Glama
thenavidm

ThriveCart MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ThriveCart MCP

No user-submitted related servers found.

    Related Servers

    • Presso MCP Server by stellagent

      Presso MCP Serverofficial

      stellagent
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects e-commerce and marketing data sources like Shopify, GA4, Google Ads, and Meta Ads to AI assistants, enabling natural language queries about store performance, ad campaigns, and customer behavior.
      7 npm
      2
      MIT

    • SalesDrive MCP Server

      dannychirkov
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with SalesDrive CRM, allowing order management, product queries, and more through natural language.
      Apache 2.0

    • WooCommerce MCP Server

      lord-dubious
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage WooCommerce stores, including products, orders, customers, categories, coupons, attributes, variations, order notes, refunds, reports, payment gateways, meta data, reviews, settings, data, posts, and system status through natural language.
      MIT

    • GoHighLevel MCP Server

      Abrahamshal
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with GoHighLevel CRM through MCP tools, with support for OAuth 2.1 remote deployment and agency multi-sub-account mode.
      -
    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 24 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: account identity, product reads, the three offer types (bump/upsell/downsell), transactions/revenue, subscription lifecycle, and affiliates. Even the similar pricing tools are clearly separated by their resource prefix. No two tools appear to do the same job.

    Naming Consistency4/5

    The naming follows a consistent list_/get_/get_<entity>_pricing pattern, with singular getters and plural listers. The only real outlier is whoami, which is a conventional exception and unlikely to cause confusion.

    Tool Count3/5

    At 24 tools, this is at the heavy end of the range, mainly because bump/upsell/downsell each get list/get/get_pricing triads. The tools are not redundant, but the surface is larger than a typical well-scoped 3–15 tool server.

    Completeness3/5

    The read side is thorough: products, all offer types, transactions, revenue, customers, and affiliates are covered. However, write coverage is thin—there is no product/offer creation or update, no customer listing, and affiliate management stops at create—so lifecycle coverage is incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources