Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Developer platforms - official Chromatic server

Chromatic published Storybook MCP server

Chromatic deploys a project's Storybook MCP server alongside each published Storybook at its /mcp route, with Chromatic access control, so teams and agents can query component documentation remotely without running Storybook locally. It runs locally with OAuth auth.

Last verified 3 tools2 sources

Install

Claude Code

About Claude Code
JSON
{
  "mcpServers": {
    "your-chromatic-storybook-mcp": {
      "type": "http",
      "url": "https://<BRANCH>--<APP-ID>.chromatic.com/mcp",
      "oauth": {
        "clientId": "cdf3737dff9d485485968e50b63fd8b4"
      }
    }
  }
}

Generic

Terminal
npx mcp-add --type http --url "https://<BRANCH>--<APP-ID>.chromatic.com/mcp" --client-id "cdf3737dff9d485485968e50b63fd8b4" --scope project

Tools

docs-list
Storybook docs tool: returns an index of components and unattached docs entries.
docs-show
Storybook docs tool: returns detailed documentation for a specific component.
docs-show-story
Storybook docs tool: returns the full story and documentation for a specific story.

As documented on October 17, 2026. A running server reports its current list through tools/list.

Notes and caveats

  • Not a separate codebase: it is the Storybook MCP addon (@storybook/addon-mcp) published by Chromatic builds.
  • Each project gets its own URL (https://<BRANCH>--<APP-ID>.chromatic.com/mcp; a default-branch permalink is recommended), so there is no single remote URL.
  • Requires Storybook 10.3 or later and React per Chromatic's setup guide, and a Chromatic project.
  • Only the Storybook Docs tools are available on the published server; Development and Testing tools need the local dev server.
  • Tool names follow the Storybook version used for the build: current Storybook docs name the docs tools docs-list, docs-show and docs-show-story, while Chromatic's setup guide still tells you to test with list-all-documentation, an earlier tool name.
  • Auth uses OAuth via CIMD where supported, otherwise a static client ID (cdf3737dff9d485485968e50b63fd8b4); a bearer token fallback is documented for clients without dynamic client registration.
  • SSO users authenticate individually.
  • Publishing is disabled by setting componentsManifest to false.
  • Chromatic does not state a beta/GA label; the underlying Storybook AI features are labelled preview.

More MCP servers for developer platforms

Related reading

FAQ

What does the Chromatic published Storybook MCP server do?

Chromatic deploys a project's Storybook MCP server alongside each published Storybook at its /mcp route, with Chromatic access control, so teams and agents can query component documentation remotely without running Storybook locally. The vendor documents 3 tools, including docs-list, docs-show and docs-show-story.

How do I add the Chromatic published Storybook MCP server to Claude Code?

Chromatic documents a Claude Code config; copy it from the Claude Code section of this page. Snippets for Generic are there too.

Does the Chromatic published Storybook MCP server need authentication?

Yes, OAuth. Transport: Streamable HTTP. Status: Unlabelled, last checked October 17, 2026.

Sources

Last verified against 2 Chromatic pages, then re-checked independently.

Newsletter

New MCP servers, the week they ship

One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.