Medusa.js-Documentation

The Medusa.js Documentation MCP Server provides access to the complete Medusa.js v2 documentation through three core MCP tools: search_docs, get_section, and list_sections. After wiring the server into your AI assistant, you can perform fuzzy searches across 2,105+ documentation sections, retrieve exact sections by title or path, and browse the full documentation catalog by category. This enables your AI assistant to answer questions with precise references, walk through setup guides, and present relevant code and configuration examples in real time. Use natural language queries to leverage the smart search, or specify a section identifier to pull exact content.

Prerequisites:

• Node.js 18+ installed on your system
• npm or yarn installed
• access to an MCP-compatible AI assistant (e.g., Claude Code CLI, Cursor, Windsurf, etc.)

Installation steps:

1. Clone the MCP server repository:

git clone https://github.com/Alexcs24/Medusa.js-Documentation-MCP-Server
cd Medusa.js-Documentation-MCP-Server

2. Install dependencies:

npm install

3. Build the TypeScript code (if applicable):

npm run build

4. Start the server locally to verify it runs (example):

node dist/index.js

5. Ensure the Medusa docs file is in place or provide a path via MEDUSA_DOCS_PATH when configuring the MCP (see configuration below).

Configuration files and environment setup (example paths):

# Path to the built server entry (adjust as needed)
dist/index.js
# Path to the Medusa docs text file used by the MCP
docs/medusa-docs.txt

Tips and common setup details:

• Ensure MEDUSA_DOCS_PATH points to the Medusa v2 documentation file (medusa-docs.txt).
• If you modify docs, rebuild the project so the latest content is loaded by the MCP.
• The MCP tools expect the server to expose a JSON-RPC interface with the three commands: search_docs, get_section, and list_sections.
• When integrating with your AI assistant, consider setting up a global or project-specific configuration similar to the examples provided in the README for Claude Code CLI, Cursor, or Windsurf.
• If you encounter path issues, use absolute paths for both the server entry and the docs file to avoid working directory discrepancies.