Medusa.js Documentation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging. Set to '1' or 'true'. | |
| MEDUSA_DOCS_PATH | No | Absolute path to the documentation file. Defaults to the included docs/medusa-docs.txt. |
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 |
|---|---|
| search_docsB | Search Medusa.js documentation for specific topics |
| get_sectionB | Get a specific documentation section by title or path |
| list_sectionsB | List all available documentation sections |
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 3 tools
Each tool has a clearly distinct purpose: listing sections, retrieving a specific section, and searching content. No overlap exists.
All tools follow a consistent verb_noun snake_case pattern (get_section, list_sections, search_docs), making naming predictable.
3 tools is well-scoped for a documentation server, covering essential operations without being too few or excessive.
The set covers listing, retrieving, and searching documentation, leaving minor gaps like filtering or navigation structure.