Commerce-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMMERCE_MCP_DB_PATH | No | Path to the SQLite database file. If unset, the server uses commerce.db in the project root. | ./commerce.db |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
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
While prefixes help distinguish the domain, boundaries between 'collect_orders' vs 'process_orders' and 'register_product' vs 'sync_product' are unclear. The absence of descriptions exacerbates ambiguity between similar verb pairs.
All 15 tools follow a rigid 'commerce_verb_noun' snake_case pattern consistently. The uniform 'commerce_' prefix creates clear namespacing and predictable structure throughout the set.
Fifteen tools is appropriate for a commerce platform covering ads, products, orders, CS, and analytics. However, without descriptions, some tools may be redundant, pushing this slightly below a perfect score.
Severe gaps in CRUD coverage: missing read/update/delete for products, orders, and ads. The surface provides creation and generation tools but lacks retrieval and modification operations necessary for a functional commerce workflow.