AIVA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set DEBUG=aiva:* environment variable for verbose logging | |
| AIVA_API_KEY | Yes | Your AIVA API key | |
| AIVA_API_URL | No | Custom API URL (default: https://api.aiva.io) | https://api.aiva.io |
| SHOPIFY_STORE | No | Your Shopify store domain | |
| SHOPIFY_ACCESS_TOKEN | No | Direct Shopify access (bypasses proxy) |
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 |
|---|---|
| aiva_get_customerC | Get customer profile by ID or email. Returns customer details, RFM segment, health score, and subscription status. |
| aiva_search_customersC | Search customers with filters. Supports filtering by segment, subscription status, tags, and more. |
| aiva_get_rfm_segmentsC | Get RFM (Recency, Frequency, Monetary) segment breakdown with customer counts and trends. |
| aiva_get_churn_riskC | Get customers at risk of churning, sorted by risk score. |
| aiva_get_subscriptionC | Get subscription details by ID or customer. |
| aiva_list_subscriptionsC | List subscriptions with filters. |
| aiva_get_delivery_scheduleC | Get upcoming deliveries for a customer or all subscriptions. |
| aiva_subscription_actionsC | Perform actions on subscriptions: pause, resume, skip, swap products. |
| aiva_get_affiliateC | Get affiliate details and stats. |
| aiva_list_affiliatesC | List affiliates with stats, sortable by performance. |
| aiva_get_referralsC | Get referral history for an affiliate. |
| shopify_get_productsC | Search and list products from the connected Shopify store. |
| shopify_get_productB | Get product details by ID or handle. |
| shopify_get_ordersC | List orders with filters. |
| shopify_get_customerC | Get Shopify customer details. |
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 15 tools
Most tools have distinct purposes, but some potential confusion exists between aiva_get_customer and aiva_search_customers (both retrieve customer data with different approaches) and between shopify_get_product and shopify_get_products (single vs. multiple retrieval). The descriptions help clarify the differences, but agents might occasionally misselect between these pairs.
All tools follow a consistent naming pattern: prefix (aiva_ or shopify_) + verb (get, list, search, or actions) + noun. This makes the tool set predictable and easy to understand, with no deviations in style or convention.
With 15 tools, the count is well-scoped for the server's purpose of managing customer and subscription data across AIVA and Shopify. It covers multiple domains without being overwhelming, and each tool appears to serve a specific, useful function.
The tool set provides strong coverage for customer, subscription, and product data retrieval, with notable features like churn risk analysis and subscription actions. Minor gaps include no update or delete operations for customers or products, and limited write capabilities beyond subscription actions, but agents can likely work around these for most workflows.