MCP Server feedback

[JesusTheHun]

After installing the MCP server and adding it to Claude Code, it struggled to connect to it: it asked for authentication, but there is none so it failed, then it couldn't connect to it... I had to disable it and enable it again for it to works.

My first impression is that it adds a great context for the agent to better understand what storybook is for and how it works, immediately after the connection.

One sad thing is that the agent doesn't communicate with it that much though, my agent started another instance of storybook to access to informations (amongst them, error logs), it would be better if it used the running instance to get those information.

It also uses a curl/python combo to grab console logs, requiring approval every time. Having the MCP to expose more rich tools would significantly improve the velocity of the agent.

Example of agents messages:

The error stack is empty in the HTML (it's populated by JS). Let me kill the extra storybook and use the Storybook MCP preview tool which connects to the right port and can capture runtime errors.

The MCP tool gives URLs but can't tell us the runtime error. Let me check the Storybook server console output more carefully by looking at Vite transform errors.

So I feel like the MCP gives general information to read about stories, but not so much to write and fix.

[sygint]

The issue seems to be due to OAuth. Has anyone else had this issue? Is there a fix from Chromatic's end or is this a config issue or something? It seems where are some open issues with Claude Code that might be related.

anthropics/claude-code#3273
anthropics/claude-code#26675

Is there documentation on this?

[sygint]

@amyrlam

[cheryl-c-tirerack]

having this issue with claude code. I can see that the mcp is deployed, but when i go through the authorization, the browser opens with
Authentication Error
invalid_target: resource is not an accepted resource for this client

You can close this window.

[xdebbie]

Same issue here too