Connect Storybook to Conductor
Workshop for building and documenting UI components in isolation. Its MCP addon lets agents look up documented components, preview stories and run component tests.
MCP serverOfficialChecked 2026-11-16
Before you start
- Conductor installed (see its MCP documentation (opens in a new tab)).
- Storybook is available on macOS, Windows and Linux. Keep its desktop app open while you work.
- Add the addon with
npx storybook add @storybook/addon-mcp, then start Storybook; the server runs athttp://localhost:6006/mcp(change the port if yours differs). The docs tools needfeatures: { componentsManifest: true }in.storybook/main.tsand a React, Angular (Vite) or Vue (Vite) framework. Storybook's AI features are in preview.
Step 1: Add Storybook to Conductor
For Claude Code sessions
Saves the server to your Claude Code user settings, so every Conductor workspace gets it.
Terminal claude mcp add --scope user --transport http storybook http://localhost:6006/mcpFor Codex sessions
Saves the server to
~/.codex/config.toml, which Codex sessions in every workspace read.Terminal codex mcp add storybook --url http://localhost:6006/mcpOr share it with your team
Add this to
.mcp.jsonat the project root and commit it. Claude Code sessions in every workspace on that branch pick it up..mcp.json { "mcpServers": { "storybook": { "type": "http", "url": "http://localhost:6006/mcp" } } }Or edit Codex's config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.storybook] url = "http://localhost:6006/mcp"Good to know- The desktop app must be open for the server to respond.
- Start a new session in Conductor after adding a server, so the agent loads it.
Step 2: Check it's connected
Terminal claude mcp listIn a Conductor session, click the plug icon in the composer or run
/mcp-statusto see each server's status.Step 3: Try a first request
Ask Conductor something that only works with Storybook connected:
Say to Conductor List the components documented in our Storybook and show me the props of the Button component.
If it doesn't work
- Conductor has no MCP settings of its own. Claude Code and Codex sessions load the same servers they use outside Conductor.
- Each workspace is a separate git worktree. Servers added with plain
claude mcp addonly apply to the folder you ran it in, so use--scope useror a committed.mcp.json. - Conductor runs on macOS. Environment variables for local servers can go in
.conductor/settings.local.toml, under[environment_variables].






