Shopify Insights MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOPIFY_TIMEZONE | No | IANA timezone override (e.g., America/New_York). Default auto-detected from store. | |
| SHOPIFY_API_VERSION | No | Shopify Admin API version. Default 2025-01. | |
| SHOPIFY_MAX_RECORDS | No | Maximum records fetched per tool call. Default 1000. | |
| SHOPIFY_SHOP_DOMAIN | Yes | Your store domain (e.g., my-store.myshopify.com) | |
| SHOPIFY_ACCESS_TOKEN | Yes | Admin API access token (starts with shpat_) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sales_summaryB | Get a sales summary with revenue, orders, and AOV. Optionally compare with previous period. |
| get_sales_comparisonB | Compare sales metrics between two explicit date ranges side by side. |
| get_revenue_breakdownC | Break down revenue by product, vendor, or product type for a given period. |
| get_inventory_alertsA | Check inventory levels across all products. Identifies out-of-stock and low-stock variants that need attention. |
| get_product_performanceA | Rank products by revenue, units sold, or order count for a given period. Shows detailed per-product metrics including AOV and share of total. |
| get_trending_productsA | Identify trending products by comparing sales between the current period and the previous one. Shows growth rates, rising stars, and declining products. |
| get_top_customersB | Rank customers by total spend or order count. Identifies VIP customers and spending patterns. |
| get_customer_segmentsA | Segment customers into VIP, Loyal, Returning, New, and Inactive based on order history and spending. Shows distribution and average spend per segment. |
| get_order_alertsA | Identify orders that require immediate attention: unfulfilled orders older than N days, financially problematic orders (refunded, voided), and high-value pending orders. |
| get_fulfillment_metricsB | Get operational metrics: fulfillment status breakdown, financial status distribution, average order value by status, and operational health indicators. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target distinct analytical questions, but there is meaningful overlap: get_sales_comparison and get_sales_summary both support period comparison, and get_product_performance, get_trending_products, and get_revenue_breakdown all examine product sales from different angles. The descriptions help, but an agent could still hesitate between these related tools.
Every tool follows the same get_<metric> snake_case pattern with clear noun phrases. The naming is entirely predictable and consistent across all ten tools.
Ten tools is a well-scoped size for a Shopify insights server. Each tool covers a meaningful analytical area without unnecessary bloat or redundancy.
The tool surface covers core merchant insights across sales, revenue, products, inventory, customers, orders, and fulfillment. It lacks direct raw order or product list retrieval, but those are outside the apparent read-only insights purpose, so the gaps are minor.