magento-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGENTO_API_DB_PATH | No | Override the default database location (~/.mcp/magento-api/database.db) | |
| MAGENTO_API_SWAGGER_PATH | No | Override the default swagger file path (data/swagger.json in package directory) |
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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_endpointsB | Search for Magento 2 REST API endpoints using keywords. Use SHORT keyword queries (1-3 words) to find endpoints by path, method, category, or description. You can optionally filter by HTTP method or category tag. |
| get_endpoint_detailsA | Get complete documentation for a specific Magento 2 REST API endpoint. Provide the exact path and optionally the HTTP method to get full details including parameters, request/response schemas. |
| list_tagsA | List all available API category tags in the Magento 2 REST API. Tags group related endpoints together (e.g., carts, customers, products, orders). |
| get_schemaB | Get the complete definition of a Magento 2 data schema/model. Schemas define the structure of request/response data objects (e.g., quote-data-cart-interface, customer-data-customer-interface). |
| search_schemasA | Search for Magento 2 data schemas by keyword. Use this to find data structure definitions by name or description (e.g., 'cart', 'customer', 'product'). |
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 5 tools
Each tool targets a distinct aspect of the Magento API: endpoints, schemas, tags, and two separate search functionalities. There is no overlap, and agents can easily differentiate them.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_endpoint_details, search_schemas). This predictability helps agents understand their purpose.
With 5 tools, the server is well-scoped for its purpose of providing Magento API documentation. The count is neither too small nor too large, and each tool serves a clear role.
The tool set covers all essential operations for exploring Magento API documentation: listing tags, searching and retrieving endpoint details, and searching and retrieving schema definitions. There are no obvious gaps.