Magento 2 GraphQL Documentation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGENTO_GRAPHQL_DOCS_PATH | No | Path to the Magento 2 GraphQL documentation directory (from commerce-webapi/src/pages/graphql). Can be absolute, relative, or home directory relative path. | |
| MAGENTO_GRAPHQL_DOCS_TOP_K | No | Number of search results to return | 5 |
| MAGENTO_GRAPHQL_DOCS_DB_PATH | No | Custom path where the SQLite database should be stored | ~/.mcp/magento-graphql-docs/database.db |
| MAGENTO_GRAPHQL_DOCS_MAX_FIELDS | No | Maximum fields per GraphQL element | 20 |
| MAGENTO_GRAPHQL_DOCS_CODE_PREVIEW | No | Maximum code preview length in characters | 400 |
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_documentationA | Search Magento 2 GraphQL documentation by keywords. Use SHORT keyword queries (1-3 words) to find documentation pages. Can filter by category, subcategory, or content type. |
| get_documentB | Retrieve complete documentation page by file path |
| search_graphql_elementsB | Search for GraphQL queries, mutations, types, or interfaces |
| get_element_detailsA | Get complete details about a specific GraphQL element |
| list_categoriesA | List all documentation categories with document counts |
| get_tutorialB | Get complete tutorial with all steps in order |
| search_examplesC | Search for code examples by topic and language |
| get_related_documentsB | Find documents related to the specified document |
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 8 tools
Each tool has a distinct purpose: retrieving documents by path, element details, related documents, tutorials, categories, and different search types. No overlap.
All tools use consistent lowercase with underscores and follow a verb_noun pattern (get_, list_, search_), with predictable naming.
8 tools is well-suited for a documentation server, covering all essential operations without excess or deficiency.
The tool set provides comprehensive coverage for documentation access: direct retrieval, tutorials, categories, and multiple search modes (keywords, examples, elements).