Skip to main content
Glama
JamBelg

MCP GraphQL Sales Server

by JamBelg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP GraphQL Sales Server

No user-submitted related servers found.

    Related Servers

    • Saleor MCP Server by saleor

      Saleor MCP Serverofficial

      saleor
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Saleor Commerce instances to fetch data about products, customers, and orders through a read-only GraphQL API integration. Supports secure authentication and domain validation for connecting to Saleor cloud instances.
      16
      AGPL 3.0

    • Shopify MCP Server

      hamzashahbaz
      A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with real-time access to Shopify store analytics, sales data, and inventory through ShopifyQL and the Admin GraphQL API. It enables users to query store performance, customer metrics, and marketing insights using natural language.
      13
      MIT

    • Database MCP Server

      hadi21k
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to safely query and explore SQL Server and PostgreSQL databases with read-only access, supporting schema discovery, relationship exploration, and query execution.
      9 npm
      3
      MIT

    • Business MCP Server

      bke1302
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to query a business database for customers, orders, and revenue using natural language through safe, well-defined tools.
      -
    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.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct query pattern: order by ID, all orders, by customer name/ID, date ranges, summary, and raw GraphQL. get_orders_by_customer_name and get_orders_by_customer_id are similar but clearly differentiated by the lookup key. graphql_query could overlap with any tool but is explicitly raw and optional.

    Naming Consistency4/5

    Most tools follow a get_* pattern (get_order_by_id, get_all_orders, get_total_spent_by_customer), but graphql_query, test_connection, and the date-based tools (orders_after_date, orders_between_dates) deviate slightly. The naming is still intuitive and readable.

    Tool Count5/5

    10 tools is a well-scoped size for a sales query server. Each tool provides a distinct, useful capability without unnecessary redundancy, and the count fits comfortably within the ideal range for a focused server.

    Completeness4/5

    The server covers a comprehensive set of order-read operations: retrieval by ID, all, customer name/ID, date filtering, total spend, and summary statistics. A raw GraphQL query tool fills in gaps. Missing write operations and customer resource tools, but for a read-focused sales query server this is substantial.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources