Turbo Docs

Provides up-to-date Turbo documentation via MCP tools for Handbook and Reference sections.

typescript

6

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "pinzonjulian-turbo-docs-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/your/Turbo-docs-mcp-server/build/index.js"
      ]
    }
  }
}

You can run a Turbo Docs MCP Server to access up-to-date Turbo documentation from your MCP client. It lets you host documentation content locally and expose it to clients like Claude Desktop or VS Code through standardized MCP configurations, enabling quick access during your conversations and code sessions.

How to use

You use an MCP client to connect to the Turbo Docs MCP Server by configuring a local or remote MCP server entry. After the server is running, the client loads the Turbo documentation tools and you can invoke them directly in conversations or code editors to browse sections like Handbook and Reference.

How to install

Prerequisites you need before installation are the following:

Node.js 18.0.0 or newer
npm (comes bundled with Node.js)

Step-by-step commands to set up the MCP server locally are shown here. Use a shell in your preferred environment and run each line separately.

With Claude Desktop

{
  "mcpServers": {
    "Turbo-docs": {
      "command": "node",
      "args": ["/path/to/your/Turbo-docs-mcp-server/build/index.js"],
      "env": {}
    }
  }
}

With VS Code

{
  "Turbo-docs": {
    "type": "stdio",
    "command": "node",
    "args": [
      "path/to/your/Turbo-docs-mcp-server"
    ]
  }
}

Troubleshooting

If you encounter issues connecting from the MCP client, verify that the path to the Node executable is correct in the configured command. If needed, replace the command with the full path to your node executable. For example, a complete path might look like: "/Users/<YOUR USER NAME>/.local/share/mise/installs/node/20.18.3/bin/node"

Available tools

handbook_introduction

Provides the Introduction content from the Handbook and enables browsing general Turbo concepts.

handbook_drive

Accesses Drive-related documentation for working with Turbo Drive features.

handbook_page_refreshes

Retrieves guidance on keeping Turbo pages up to date with Page Refreshes.

handbook_frames

Shows how Frames are used within Turbo documentation and examples.

handbook_streams

Provides information about Streams in Turbo documentation.

handbook_native

Gives information on Native integrations and usage within Turbo.

handbook_building_with_turbo

Explains building projects with Turbo tooling and workflows.

handbook_installing_turbo

Details steps to install Turbo in various environments.

reference_attributes

Lists and explains documented Attributes used in Turbo components.

reference_drive

Details Drive-related API and usage within Turbo.

reference_events

Describes events that Turbo components can emit and respond to.

reference_frames

Outlines how Frames are defined and used in Turbo documentation.

reference_streams

Covers Streams in the Turbo ecosystem and their interactions.