Skip to content

Connect Storybook to Codex

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

  • Codex 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 Codex

    Add it from the terminal

    Saves the server to ~/.codex/config.toml, so it works in every project.

    Terminal
    codex mcp add storybook --url http://localhost:6006/mcp

    Or edit the 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.
  2. Step 2: Check it's connected

    Terminal
    codex mcp list

    In a Codex session, run /mcp to see connected servers and their tools.

  3. Step 3: Try a first request

    Ask Codex something that only works with Storybook connected:

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

If it doesn't work

  • Codex reads ~/.codex/config.toml. A project .codex/config.toml is only read in projects you have trusted.
  • Codex doesn't expand ~ or environment variables in command. Use a full path in the config file.
  • Servers that need a sign-in: run codex mcp login <name>.