Turbo Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| handbook-introductionB | Introduction to Turbo - learn about HTML-over-the-wire approach, persistent processes, and how Turbo Drive, Frames, Streams, and Native work together to create fast web applications without heavy JavaScript frameworks |
| handbook-driveB | Turbo Drive navigation guide - covers page visits, application/restoration visits, link handling, form submissions, progress indicators, caching, prefetching, and view transitions for fast page navigation |
| handbook-page-refreshesC | Page refresh techniques with morphing - learn about smooth page updates using DOM morphing with idiomorph, scroll preservation, excluding sections from morphing, and broadcasting refresh streams |
| handbook-framesC | Turbo Frames for page decomposition - covers independent page segments, scoped navigation, eager/lazy loading, cache benefits, targeting navigation, frame promotion to visits, and custom rendering |
| handbook-streamsC | Turbo Streams for live updates - learn about the 9 stream actions (append, prepend, replace, update, remove, before, after, morph, refresh), WebSocket/SSE integration, and server-side template reuse |
| handbook-nativeB | Hotwire Native for mobile apps - overview of iOS and Android native app development using Turbo-enabled web views for hybrid applications with native navigation and web content |
| handbook-buildingC | Building Turbo applications - covers script handling, JavaScript bundling, caching strategies, installing behavior with Stimulus, making transformations idempotent, and persisting elements across page loads |
| handbook-installingB | Installing Turbo in your application - covers CDN installation, npm package setup, bundler integration, importing strategies, and Rails-specific installation with turbo-rails gem |
| reference-attributesB | Complete reference for Turbo data attributes and meta tags - covers all data-turbo-* attributes for controlling Drive behavior, frame navigation, caching, and automatically added attributes like aria-busy |
| reference-driveB | Turbo Drive API reference - detailed documentation of Drive methods, configuration options, and programmatic control of navigation behavior |
| reference-eventsB | Turbo events reference - comprehensive list of all Turbo events fired during navigation, form submissions, frame updates, and stream processing for lifecycle management |
| reference-framesB | Turbo Frames API reference - detailed frame element attributes, JavaScript methods, lifecycle callbacks, and programmatic frame control |
| reference-streamsB | Turbo Streams API reference - complete documentation of stream actions, JavaScript methods, custom action creation, and programmatic stream handling |
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 13 tools
Every tool has a clearly distinct purpose with no overlap. The 'handbook-' tools cover conceptual topics and tutorials, while the 'reference-' tools provide API documentation, making it impossible to confuse them. Each tool name directly indicates its specific scope within the Turbo framework.
The naming follows a perfect and predictable pattern throughout. All tools use a consistent 'prefix-topic' format with kebab-case, where 'handbook-' indicates conceptual guides and 'reference-' indicates API documentation. This consistency makes the tool set highly readable and predictable.
With 13 tools, the count is well-scoped and appropriate for the server's purpose of documenting Turbo. It covers all major aspects (Drive, Frames, Streams, Native, installation, attributes, events) without being overwhelming, and each tool earns its place by addressing a distinct area of the framework.
The tool set provides complete coverage of the Turbo documentation domain. It includes all core concepts (introduction, building, installing, Drive, Frames, Streams, Native, page refreshes) and comprehensive API references (attributes, Drive, events, Frames, Streams), leaving no gaps for agents to navigate the framework effectively.