@storybook/addon-mcp 0.3.4 → 0.4.1

package/README.md

@@ -1,226 +1,11 @@
 # Storybook MCP Addon
 
-This Storybook addon runs an MCP (Model Context Protocol) server to help develop UI components more efficiently.
-
-It enables a workflow where for each UI component created, the agent will automatically generate and link to example stories. These stories let you visually verify the new UI in each of its key states, and provide documentation and component tests.
-
-The addon provides tools to improve agents' UI development capabilities, retrieve story URLs, and access component documentation.
+Storybook addon for MCP-powered UI development workflows.
 
 <div align="center">
-   <img src="./addon-mcp-claude-code-showcase.gif" alt="Storybook MCP Addon Demo" />
+	<img src="./addon-mcp-claude-code-showcase.gif" alt="Storybook MCP Addon Demo" />
 </div>
 
-## Getting Started
-
-### Installation and Setup
-
-> [!NOTE]
-> This addon requires Storybook version 9.1.16 or higher.
-
-Use Storybook's CLI to automatically install and configure the addon:
-
-```bash
-npx storybook add @storybook/addon-mcp
-```
-
-This command will install the addon and add it to your Storybook configuration automatically.
-
-Start your Storybook development server:
-
-```bash
-npm run storybook
-```
-
-The MCP server will be available at `<your_storybook_dev_server_origin>/mcp` when Storybook is running.
-
-### Configuration
-
-#### Addon Options
-
-You can configure which toolsets are enabled by default in your `.storybook/main.js`:
-
-```javascript
-// .storybook/main.js
-export default {
-	addons: [
-		{
-			name: '@storybook/addon-mcp',
-			options: {
-				toolsets: {
-					dev: true, // Tools for story URL retrieval and UI building instructions (default: true)
-					docs: true, // Tools for component manifest and documentation (default: true)
-				},
-			},
-		},
-	],
-	// componentsManifest is enabled by default in recent Storybook versions, no need to set it
-};
-```
-
-**Available Toolsets:**
-
-- `dev`: Enables [Dev Tools](#dev-tools)
-- `docs`: Enables [Documentation Tools](#docs-tools)
-
-Disabling the Dev Tools is useful when you want to try out the same experience that your external component consumers will get, because they only get the Component Documentation Tools.
-
-#### Configuring toolsets with headers
-
-You can also configure the available toolsets when setting up the MCP Server in your MCP Client by setting the `X-MCP-Toolsets` header. The header is a comma-separated list of toolset names, `X-MCP-Toolsets: dev,docs`. Eg. to configure your client to only have the Component Documentation Tools, the `.mcp.json`-file could look like this (format depends on the exact client you're using):
-
-```json
-{
-	"storybook-mcp": {
-		"url": "http://localhost:6006/mcp",
-		"type": "http",
-		"headers": {
-			"X-MCP-Toolsets": "docs"
-		}
-	}
-}
-```
-
-### Configuring Your Agent
-
-> [!NOTE]
-> This addon is primarily tested with Claude Code and GitHub Copilot. While it should work with other MCP clients, Claude Code is our main target for compatibility and testing.
-
-#### Claude Code Setup
-
-To use this addon with [Claude Code](https://claude.ai/code), use the built-in MCP configuration command:
-
-1. **Add the MCP server**: Run the following command in your terminal:
-
-   ```bash
-   claude mcp add storybook-mcp --transport http http://localhost:6006/mcp --scope project
-   ```
-
-2. **Start Storybook**: Make sure your Storybook development server is running:
-
-   ```bash
-   npm run storybook
-   ```
-
-3. **Connect Claude Code**: Claude Code should automatically detect and connect to the MCP server when it's running. You can verify the connection by asking Claude to use Storybook-related tools.
-
-4. **Configure Agent Behavior** (Optional but Recommended): Add the following system or project prompt to ensure your agent uses the Storybook tools when appropriate:
-
-```
-Before doing any UI, frontend or React development, ALWAYS call the storybook MCP server to get further instructions.
-```
-
-#### Other MCP Clients
-
-[![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en-US/install-mcp?name=storybook-mcp&config=eyJ1cmwiOiJodHRwOi8vbG9jYWxob3N0OjYwMDYvbWNwIn0%3D)
-
-This addon should work with any MCP-compatible client that supports the `tool` capability and the `streamable-http` transport. Here are setup guides for other popular clients:
-
-- [GitHub Copilot](https://docs.github.com/en/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp)
-- [Cursor](https://docs.cursor.com/en/context/mcp#installing-mcp-servers)
-- [opencode](https://opencode.ai/docs/mcp-servers/)
-- [Claude Desktop](https://modelcontextprotocol.io/quickstart/user)
-- [Cline](https://docs.cline.bot/mcp/configuring-mcp-servers)
-- [Zed Editor](https://zed.dev/docs/ai/mcp#as-custom-servers)
-- [Continue](https://docs.continue.dev/customize/deep-dives/mcp#how-to-configure-mcp-servers)
-- [Codex](https://github.com/openai/codex/blob/main/docs/config.md#mcp_servers)
-
-For clients not listed above, consult their documentation for MCP server configuration. The server configuration typically requires:
-
-- **Server Type**: `http`
-- **URL**: `http://localhost:6006/mcp` (adjust port if your Storybook runs on a different port)
-- ⚠️ Make sure your Storybook development server is running before your agent tries to connect.
-
-## Usage
-
-This addon provides MCP tools that your agent can use. The goal is that the agent uses these tools automatically when doing UI development, but agents are unreliable and unpredictable, so sometimes you might need to explicitly tell it to use the tools.
-
-**If you are prompting from an IDE like VSCode or Cursor, be sure to use `Agent` mode and `sonnet-4.5` or better.**
-
-### Dev Tools
-
-These tools are always available when the addon is installed:
-
-#### 1. UI Building Instructions (`get_ui_building_instructions`)
-
-Provides agents with standardized instructions for UI component development within your project. This tool returns guidelines for:
-
-- Writing Storybook stories using CSF3 format
-- Component development best practices
-- Story linking requirements
-
-The instructions ensure agents follow your project's conventions when creating or modifying UI components and their corresponding stories.
-
-#### 2. Preview Stories (`preview-stories`)
-
-Allows agents to retrieve direct URLs to specific stories in your Storybook. The agent can request URLs for multiple stories by providing:
-
-- **Path-based input** (best when the agent is already editing a `.stories.*` file):
-  - `absoluteStoryPath`: Absolute path to the story file
-  - `exportName`: The export name of the story
-  - `explicitStoryName`: Optional explicit story name
-- **ID-based input** (best when the agent discovered stories via docs tools):
-  - `storyId`: Full Storybook story ID (for example `example-button--primary`)
-
-Example agent usage:
-
-```
-Prompt: I need to see the primary variant of the Button component
-
-Agent calls tool, gets response:
-http://localhost:6006/?path=/story/example-button--primary
-```
-
-### Docs Tools
-
-These additional tools are available when the component manifest feature is enabled. They provide agents with detailed documentation about your UI components.
-
-**Requirements:**
-
-- Storybook version 10.1.0 or higher (currently only available as prereleases, `storybook@next`)
-- React-based framework (`react-vite`, `nextjs-vite`, `nextjs`, `react-webpack5`)
-- Feature flag `features.componentsManifest` enabled (defaults to `true` in recent Storybook versions)
-
-**To enable:**
-
-The `componentsManifest` feature is enabled by default in recent Storybook versions — no configuration needed.
-
-If you are on an older Storybook version that doesn't default to `true`, you may need to enable it explicitly. Use the flag that matches your Storybook version:
-
-```javascript
-// .storybook/main.js
-export default {
-	// ... other config
-	features: {
-		// For Storybook 10.3.x and later:
-		componentsManifest: true,
-		// For older Storybook versions (before the flag was renamed):
-		// experimentalComponentsManifest: true,
-	},
-};
-```
-
-#### 3. List All Documentation (`list-all-documentation`)
-
-Returns a list of all available UI components as well as standalone docs in your component library. Useful for the LLM as discovery and understanding what components are available to use.
-
-You can pass `withStoryIds: true` to include nested story entries (story name + story ID) under each component, which is useful before calling `preview-stories` or `run-story-tests` with `storyId`.
-
-#### 4. Get Documentation (`get-documentation`)
-
-Retrieves detailed documentation for a specific component or docs entry.
-
-Component documentation includes component ID and story IDs for listed stories, so agents can directly feed those IDs into `preview-stories` and `run-story-tests`.
-
-The agent provides a component/docs ID to retrieve its documentation. To get documentation for multiple entries, call this tool multiple times.
-
-## Contributing
-
-We welcome contributions to improve Storybook's agent integration, within or outside of this addon! Here's how you can help:
-
-1. **Ideas and feature requests**: If you have ideas for what else we could do to improve the Storybook experience when using agents, please [start a discussion](https://github.com/storybookjs/mcp/discussions/new?category=ideas) in this repository.
-
-2. **Report Issues**: If you find bugs, please open an issue on our [GitHub repository](https://github.com/storybookjs/mcp), but keep in mind that this is currently highly experimental, explorative and probably filled with bugs.
-
-3. **Development**:
+See [documentation](https://storybook.js.org/docs/next/ai/mcp/overview/?ref=readme) for installation instructions, usage examples, APIs, and more.
 
-See [the monorepo readme](https://github.com/storybookjs/mcp#-quick-start).
+Learn more about Storybook at [storybook.js.org](https://storybook.js.org/?ref=readme).

package/dist/preset.js

@@ -9,13 +9,13 @@ import { stringify } from "picoquery";
 import path from "node:path";
 import { normalizeStoryPath } from "storybook/internal/common";
 import { storyNameFromExport } from "storybook/internal/csf";
-import { ComponentManifestMap, DocsManifestMap, GET_TOOL_NAME, LIST_TOOL_NAME, addGetDocumentationTool, addGetStoryDocumentationTool, addListAllDocumentationTool } from "@storybook/mcp";
+import { ComponentManifestMap, DocsManifestMap, GET_TOOL_NAME, LIST_TOOL_NAME, STORYBOOK_MCP_INSTRUCTIONS, addGetDocumentationTool, addGetStoryDocumentationTool, addListAllDocumentationTool } from "@storybook/mcp";
 import fs from "node:fs/promises";
 import { buffer } from "node:stream/consumers";
 
 //#region package.json
 var name = "@storybook/addon-mcp";
-var version = "0.3.4";
+var version = "0.4.1";
 var description = "Help agents automatically write and test stories for your UI components";
 
 //#endregion
@@ -768,7 +768,7 @@ const getManifestStatus = async (options) => {
 		options.presets.apply("experimental_manifests", void 0, { manifestEntries: [] }),
 		options.presets.apply("experimental_componentManifestGenerator")
 	]);
-	const hasManifests = !!manifests || !!legacyComponentManifestGenerator;
+	const hasManifests = manifests && "components" in manifests || !!legacyComponentManifestGenerator;
 	const hasFeatureFlag = !!(features?.componentsManifest ?? features?.experimentalComponentsManifest);
 	return {
 		available: hasFeatureFlag && hasManifests,
@@ -831,6 +831,25 @@ function estimateTokens(text) {
 	return tokenCount;
 }
 
+//#endregion
+//#region src/instructions/dev-instructions.md
+var dev_instructions_default = "## UI Building and Story Writing Workflow\n\n- Before creating or editing components or stories, call **get-storybook-story-instructions**.\n- Treat that tool's output as the source of truth for framework-specific imports, story patterns, and testing conventions.\n- After changing any component or story, call **preview-stories**.\n- Always include every returned preview URL in your user-facing response so the user can verify the visual result.\n";
+
+//#endregion
+//#region src/instructions/test-instructions.md
+var test_instructions_default = "## Validation Workflow\n\n- After each component or story change, run **run-story-tests**.\n- Use focused runs while iterating, then run a broad pass before final handoff when scope is unclear or wide.\n- Fix failing tests before reporting success. Do not report completion while story tests are failing.\n";
+
+//#endregion
+//#region src/instructions/build-server-instructions.ts
+function buildServerInstructions(options) {
+	const sections = ["Follow these workflows when working with UI and/or Storybook."];
+	if (options.devEnabled) sections.push(dev_instructions_default.trim());
+	if (options.testEnabled) sections.push(test_instructions_default.trim());
+	if (options.docsEnabled) sections.push(STORYBOOK_MCP_INSTRUCTIONS.trim());
+	if (sections.length === 1) return "";
+	return sections.join("\n\n");
+}
+
 //#endregion
 //#region src/mcp-handler.ts
 let transport;
@@ -840,17 +859,29 @@ let disableTelemetry;
 let a11yEnabled;
 const initializeMCPServer = async (options, multiSource) => {
 	disableTelemetry = (await options.presets.apply("core", {}))?.disableTelemetry ?? false;
-	const server = new McpServer({
-		name,
-		version,
-		description
-	}, {
+	const addonVitestConstants = await getAddonVitestConstants();
+	const manifestStatus = await getManifestStatus(options);
+	a11yEnabled = await isAddonA11yEnabled(options);
+	let server;
+	const serverOptions = {
 		adapter: new ValibotJsonSchemaAdapter(),
+		get instructions() {
+			return buildServerInstructions({
+				devEnabled: server?.ctx.custom?.toolsets?.dev ?? true,
+				testEnabled: (server?.ctx.custom?.toolsets?.test ?? true) && !!addonVitestConstants,
+				docsEnabled: (server?.ctx.custom?.toolsets?.docs ?? true) && manifestStatus.available
+			});
+		},
 		capabilities: {
 			tools: { listChanged: true },
 			resources: { listChanged: true }
 		}
-	}).withContext();
+	};
+	server = new McpServer({
+		name,
+		version,
+		description
+	}, serverOptions).withContext();
 	if (!disableTelemetry) server.on("initialize", async () => {
 		await collectTelemetry({
 			event: "session:initialized",
@@ -859,9 +890,8 @@ const initializeMCPServer = async (options, multiSource) => {
 	});
 	await addPreviewStoriesTool(server);
 	await addGetUIBuildingInstructionsTool(server);
-	a11yEnabled = await isAddonA11yEnabled(options);
 	await addRunStoryTestsTool(server, { a11yEnabled });
-	if ((await getManifestStatus(options)).available) {
+	if (manifestStatus.available) {
 		logger.info("Experimental components manifest feature detected - registering component tools");
 		const contextAwareEnabled = () => server.ctx.custom?.toolsets?.docs ?? true;
 		await addListAllDocumentationTool(server, contextAwareEnabled);
@@ -1298,7 +1328,7 @@ const experimental_devServer = async (app, options) => {
 				This toolset is only supported in React-based setups.
 			</div>`;
 		else if (!manifestStatus.hasFeatureFlag) docsNotice = `<div class="toolset-notice">
-				This toolset requires enabling the experimental component manifest feature.
+				This toolset requires enabling the component manifest feature.
 				<a target="_blank" href="https://github.com/storybookjs/mcp/tree/main/packages/addon-mcp#docs-tools-experimental">Learn how to enable it</a>
 			</div>`;
 		const testNoticeLines = [!addonVitestConstants && `This toolset requires Storybook 10.3.0+ with <code>@storybook/addon-vitest</code>. <a target="_blank" href="https://storybook.js.org/docs/writing-tests/test-addon">Learn how to set it up</a>`, !a11yEnabled && `Add <code>@storybook/addon-a11y</code> for accessibility testing. <a target="_blank" href="https://storybook.js.org/docs/writing-tests/accessibility-testing">Learn more</a>`].filter(Boolean);

package/dist/preview-stories-app-script.js

@@ -4,7 +4,7 @@ const MCP_APP_SIZE_CHANGED_EVENT = "storybook-mcp:size-changed";
 
 //#endregion
 //#region package.json
-var version = "0.3.4";
+var version = "0.4.1";
 
 //#endregion
 //#region src/tools/preview-stories/preview-stories-app-script.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@storybook/addon-mcp",
-  "version": "0.3.4",
+  "version": "0.4.1",
   "description": "Help agents automatically write and test stories for your UI components",
   "keywords": [
     "ai",
@@ -34,12 +34,12 @@
     "picoquery": "^2.5.0",
     "tmcp": "^1.16.0",
     "valibot": "1.2.0",
-    "@storybook/mcp": "0.5.1"
+    "@storybook/mcp": "0.6.1"
   },
   "devDependencies": {
-    "@storybook/addon-a11y": "10.3.0-alpha.12",
-    "@storybook/addon-vitest": "10.3.0-alpha.12",
-    "storybook": "10.3.0-alpha.12"
+    "@storybook/addon-a11y": "10.3.0-alpha.16",
+    "@storybook/addon-vitest": "10.3.0-alpha.16",
+    "storybook": "10.3.0-alpha.16"
   },
   "peerDependencies": {
     "@storybook/addon-vitest": "^9.1.16 || ^10.0.0 || ^10.1.0-0 || ^10.2.0-0 || ^10.3.0-0 || ^10.4.0-0",