shopops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for HTTP transport (default 8080). | 8080 |
| MCP_LOG_LEVEL | No | Logging verbosity (error, warn, info, debug). | |
| SHOPIFY_API_KEY | No | Shopify private app API key (required for Shopify store). | |
| MCP_PRICING_MODEL | No | Pricing strategy (default margin_based). | margin_based |
| MCP_REPORT_S3_BUCKET | No | If provided, daily/weekly reports are uploaded to the specified S3 bucket. | |
| SHOPIFY_API_PASSWORD | No | Shopify private app password (required for Shopify store). | |
| SHOPIFY_STORE_DOMAIN | No | Shopify store domain (e.g., myshop.myshopify.com) (required for Shopify store). | |
| WOOCOMMERCE_STORE_URL | No | WooCommerce store URL (e.g., https://example.com) (required for WooCommerce store). | |
| LEMONSQUEEZY_LICENSE_KEY | No | Pro license key for unlocking advanced tools. | |
| MCP_ENABLE_ANONYMIZATION | No | When set to true, personally identifiable data is masked in reports. | |
| MCP_FORECAST_WINDOW_DAYS | No | Number of days to forecast (default 30). | 30 |
| WOOCOMMERCE_CONSUMER_KEY | No | WooCommerce REST API consumer key (required for WooCommerce store). | |
| WOOCOMMERCE_CONSUMER_SECRET | No | WooCommerce REST API consumer secret (required for WooCommerce store). |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_connectA | Manage Shopify or WooCommerce store connections. action="connect" adds a new store and performs an initial sync of products, orders, and customers; action="sync" refreshes cached data for an existing store; action="list" returns all connected stores with their sync counts. Returns a JSON payload with store metadata (id, name, platform, url, counts, last_sync) — credentials are never returned. |
| store_demo_seedA | Create a realistic demo store populated with 20 products, 40 customers across 6 archetype buckets (champions, loyal, new, at-risk, hibernating, one-off), and 150+ orders spanning the last 6 months. Use this to explore ShopOps without real Shopify or WooCommerce credentials — every tool (inventory_status, customers_segment, order_anomalies, report_weekly, etc.) will return meaningful output on the returned store_id. Safe to call multiple times; each call creates a new demo store with a unique ID. Returns the store_id plus product/customer/order counts. |
| inventory_statusA | Snapshot of current stock levels for a connected store. Returns a summary object with total product count, out-of-stock count, low-stock count (≤10 units), plus two arrays: out_of_stock and low_stock — each containing product id, title, sku, quantity, and status. Items are sorted by urgency (lowest quantity first). Read-only and idempotent. |
| inventory_forecastA | Predict stock depletion dates using moving-average sales velocity. Returns reorder points, safety stock levels, and suggested reorder quantities for each product. |
| pricing_analyzeA | Analyze pricing across products with margin calculation, sales velocity, and rule-based price optimization suggestions. Returns an array where each element contains product_title, current_price, cost, margin_percent, daily_units_sold, revenue_per_day, suggested_price (or null if no change recommended), and suggestion_reason. Pass product_id to scope to a single product, omit for full catalog. |
| pricing_optimizeA | Filtered pricing recommendations — only products where a price change is suggested. Returns a summary with total_suggestions count and an optimizations array (product, current_price, suggested_price, change_percent, reason, daily_revenue), sorted by absolute change_percent (biggest moves first). Use this instead of pricing_analyze when you only want actionable changes. |
| customers_segmentA | RFM (Recency, Frequency, Monetary) customer segmentation. Categorizes customers into segments: Champions, Loyal, Potential, At Risk, New, Hibernating, Lost — with actionable recommendations. |
| customers_churnA | Identify customers at risk of churning based on RFM recency + frequency signals. Returns an object with at_risk, hibernating, and lost arrays — each contains customer id, name, email, last_order_date, days_since_last_order, total_spent, total_orders, and a win_back_recommendation string. Use this for targeted re-engagement campaigns. |
| order_anomaliesA | Statistical anomaly detection on recent orders. Flags high-value orders (>3σ from mean), velocity spikes (customer ordering unusually fast), unusual quantities, off-hours purchases (2am-5am), and new-customer high-value orders. Returns an array of anomalies with order_id, anomaly_type, severity (low/medium/high), reason, and recommended_action. Useful for fraud detection and revenue spike investigation. |
| product_performanceA | Product performance report with ABC analysis. Category A = top 80% revenue, B = next 15%, C = bottom 5%. Includes trends, margins, and daily sales velocity. |
| report_dailyA | Daily operational report: orders, revenue, top products, new vs returning customers, low stock alerts, and anomaly count. |
| report_weeklyA | Weekly trend report: revenue/order changes vs previous week, customer segment distribution, trending products, and AI-generated insights. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| inventory_alert | Scan inventory for low stock, stockout risks, and reorder recommendations using demand forecasting. |
| sales_summary | Generate a comprehensive sales report with product performance, customer segments, and trend analysis. |
| customer_retention | Identify at-risk customers, analyze churn signals, and generate retention strategies using RFM segmentation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| store_overview | Connected stores summary with product/order/customer counts |
| store_inventory | Products with low or zero stock across all stores |
| store_recent_orders | Last 20 orders across all stores |
| store_top_customers | Top 20 customers by total spending across all stores |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/enzoemir1/shopops-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server