Stimulus 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-originB | Learn why Stimulus was created by DHH - covers the philosophy of modest JavaScript frameworks, server-rendered HTML, and how Stimulus differs from mainstream JavaScript frameworks like React |
| handbook-introductionB | Introduction to Stimulus core concepts: controllers, actions, targets, and values. Explains how Stimulus enhances server-rendered HTML and separates content from behavior |
| handbook-helloB | Step-by-step tutorial for building your first Stimulus controller - covers creating a greeting controller with targets, actions, and DOM event handling |
| handbook-buildingB | Build a real-world clipboard controller example - demonstrates practical Stimulus patterns, CSS classes, and connecting JavaScript to HTML elements |
| handbook-resilienceB | Best practices for building robust Stimulus applications - covers progressive enhancement, graceful degradation, and handling edge cases |
| handbook-stateC | Learn how Stimulus manages state through values and data attributes - covers reactive programming patterns and keeping state in sync with the DOM |
| handbook-externalC | Techniques for integrating external APIs and resources - covers AJAX requests, working with third-party libraries, and asynchronous operations |
| handbook-installingB | Complete guide to installing Stimulus in your application - covers Webpack, import maps, Rails integration, and manual setup options |
| reference-actionsC | Complete reference for Stimulus actions - covers action descriptors, event handling, keyboard filters, global events, action parameters, and event options like :prevent and :stop |
| reference-controllersC | Controller API reference - covers controller lifecycle, scopes, nested controllers, cross-controller communication with events, and registration patterns |
| reference-css-classesC | CSS classes API reference - learn how to dynamically manage CSS classes in Stimulus controllers for styling and visual state management |
| reference-lifecycleB | Controller lifecycle callbacks reference - covers connect(), disconnect(), and target connection/disconnection callbacks for managing controller state |
| reference-outletsC | Outlets API reference - learn how to connect controllers to each other for component communication and coordination between different parts of your application |
| reference-targetsC | Targets API reference - covers target definitions, properties (singular/plural/existential), shared targets, optional targets, and target lifecycle callbacks |
| reference-typescriptB | TypeScript integration guide - covers type definitions, strongly typed targets/values/outlets, and best practices for using Stimulus with TypeScript |
| reference-valuesB | Values API reference - covers value definitions, type coercion, change callbacks, and using values for reactive data binding between HTML and JavaScript |
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 16 tools
Every tool has a clearly distinct purpose with no ambiguity. The 'handbook-' tools are tutorial-focused covering different aspects like installation, concepts, and best practices, while the 'reference-' tools are API-focused covering specific features like actions, controllers, and values. There is no overlap in functionality between tools.
Tool names follow a highly consistent pattern throughout. All tools use a prefix ('handbook-' or 'reference-') followed by a descriptive noun or concept, with consistent kebab-case formatting. This predictable structure makes it easy to understand the tool's category and purpose at a glance.
The 16 tools are well-scoped for a documentation server covering both tutorial and reference material. Each tool earns its place by addressing a specific aspect of Stimulus, from introductory tutorials to detailed API references, without feeling excessive or insufficient for the domain.
The tool surface provides complete coverage for a Stimulus documentation server. It includes both tutorial tools for learning (installation, concepts, examples) and comprehensive reference tools for all major API features (controllers, actions, targets, values, etc.), with no obvious gaps in the domain.