Skip to content

Connect Storybook to VS Code

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

  • VS Code 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 at http://localhost:6006/mcp (change the port if yours differs). The docs tools need features: { componentsManifest: true } in .storybook/main.ts and a React, Angular (Vite) or Vue (Vite) framework. Storybook's AI features are in preview.
  1. Step 1: Add Storybook to VS Code

    Add it from the terminal

    Adds the server to your VS Code profile, so it works in every workspace.

    Terminal
    code --add-mcp '{"name":"storybook","type":"http","url":"http://localhost:6006/mcp"}'

    Or add it to the workspace

    Add this to .vscode/mcp.json and commit it to share it with your team.

    .vscode/mcp.json
    {
      "servers": {
        "storybook": {
          "type": "http",
          "url": "http://localhost:6006/mcp"
        }
      }
    }
    Good to know
    • The desktop app must be open for the server to respond.
  2. Step 2: Check it's connected

    Run MCP: List Servers from the Command Palette, then open Copilot Chat in Agent mode and check the tools picker.

  3. Step 3: Try a first request

    Ask VS Code something that only works with Storybook connected:

    Say to VS Code
    List the components documented in our Storybook and show me the props of the Button component.

If it doesn't work

  • VS Code asks you to trust a server the first time it starts. Accept it, or the tools stay hidden.
  • code --add-mcp writes to your user profile, so the server works in every workspace.
  • Use MCP: List Servers → Show Output to see startup errors.