Cart MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CART_API_KEY | Yes | Your Cart API key (starts with cart_sk_) | |
| CART_API_BASE_URL | No | Override the API base URL (defaults to https://api.usecart.com/v1) | https://api.usecart.com/v1 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_storesA | Search the Cart database of e-commerce stores. Filter by keyword, platform (e.g. shopify, woocommerce), language, minimum traffic, and more. Returns a paginated list of store summaries with traffic metrics, product counts, and platform info. |
| get_storeA | Get the full profile for a single e-commerce store by its domain. Returns detailed info including traffic stats, product count, platform, social links, business model flags (dropshipping, print-on-demand), and more. |
| get_store_productsA | List products sold by a specific e-commerce store. Returns a paginated list of product titles, prices, images, and vendors. |
| get_store_trafficA | Get detailed traffic analytics for a store, including monthly visitors, trend percentage, bounce rate, average visit length, pages per visit, geographic breakdown, and traffic sources (direct, search, social, mail, display, referrals). |
| get_store_techA | Get the technology stack used by a store. Returns a list of technologies with their categories (e.g. analytics, payments, marketing, hosting). |
| get_store_adsB | Get advertisements detected for a specific store. Returns ad creatives with platform, image URL, landing URL, and date range when the ad was active. |
| compare_storesA | Compare 2 to 10 e-commerce stores side by side. Returns full store profiles for each domain so you can compare traffic, products, platforms, and more. |
| search_productsA | Search the Cart product database across all tracked stores. Filter by keyword, price range, and currency. Returns product titles, prices, images, store domain, and vendor. |
| get_productA | Get full details for a single product by its Cart product ID. Returns the product title, price, image, vendor, store domain, and timestamps. |
| get_trendingA | Get trending products and rapidly growing stores. Useful for identifying hot products, emerging niches, and fast-rising stores. |
| search_adsA | Search for e-commerce advertisements across platforms. Filter by keyword or store domain. Returns ad creatives with platform, images, landing URLs, and active date ranges. |
| get_adC | Get full details for a single advertisement by its Cart ad ID. |
| search_suppliersB | Search for product suppliers and vendors. Filter by keyword, location, or type. Useful for finding sourcing and manufacturing partners. |
| get_niche_overviewA | Get a market overview for a niche keyword. Returns the total number of stores and products in the niche, average price, top stores, and trending products. Great for market research and competitive analysis. |
| get_accountA | Get information about the authenticated Cart API account, including the current plan, email, daily request count, and request limit. Use this to check remaining API quota. |
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
All 15 tools have distinct, non-overlapping purposes. For example, search_stores vs get_store search vs detail; get_store_products vs search_products differentiate by store-specific vs cross-store; and get_store_traffic, tech, ads each address unique aspects. No confusion between tools.
Every tool uses a consistent verb_noun snake_case pattern (e.g., search_stores, get_store, get_store_products, compare_stores). Verbs are appropriately chosen ('search', 'get', 'compare'), and the naming is uniformly descriptive and predictable.
With 15 tools, the server is well-scoped for its domain of e-commerce store and product intelligence. Each tool covers a specific operation without unnecessary duplication, and the count feels neither sparse nor overwhelming.
The tool set provides comprehensive coverage for the intended use case: retrieving store profiles, detailed analytics, product data, ads, supplier info, trends, and niche overviews. No obvious gaps exist—all major data types and operations (search, detail, compare, trending) are represented.