turbo-docs

This MCP server exposes Turbo’s documentation inside your MCP-enabled client. It compiles the Turbo docs into accessible tools organized under two primary sections: Handbook and Reference. Each section is exposed as its own tool, allowing you to retrieve specific content such as Introduction, Drive, Page Refreshes, Frames, Streams, Native features, Building with Turbo, Installing Turbo, and Reference topics like Attributes, Drive, Events, Frames, and Streams. To use it, start the built server as described in the installation steps, then configure your MCP client (Claude Desktop or VS Code) to point at the built index.js. Once connected, you can invoke the individual documentation tools to fetch up-to-date Turbo documentation directly within your conversations or editor sessions.

Prerequisites:

• Node.js v18.0.0 or higher
• npm (bundled with Node.js)

Installation and setup:

1. Clone the repository and navigate to the project directory.
2. Install dependencies: npm install
3. Build the project: npm run build This compiles the TypeScript source and outputs the executable to the build/ directory. Use the path to build/index.js when configuring the MCP client.
4. Start the MCP server (or ensure the built index.js is accessible at the specified path in your MCP client configuration).

Tips and common issues:

• Ensure Node.js is accessible in your system PATH, or use the full path to node in your MCP configuration if you encounter ENOENT errors.
• If you see ENOENT errors like spawn node ENOENT, provide the absolute path to the node executable in the command field.
• The server is marked experimental; expect potential instability or breaking changes during development.
• Replace /path/to/your/Turbo-docs-mcp-server with the actual path to the project before starting Claude Desktop or VS Code configurations.
• The build output will be located in the build/ directory; point your MCP client to build/index.js.
• If you plan to run in production, consider pinning the Node.js version and documenting the exact path to node to avoid PATH-related issues.