◎ Discry Score
storybook.com
devtools · API
B
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 96 (A)
Discry your API →
DEVTOOLS · RANK #11 OF 39

Storybook is Good to agents.

Discry independently scored how well an AI agent can discover and understand the Storybook API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 71/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Fail
llms.txtAn llms.txt index that points agents to the docs that matter.Pass
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Pass
llms-full.txtA full-text bundle agents can load in one request.Pass
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Pass
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Pass

Comprehension

55% of score · 100/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass
Realistic examplesRunnable, real-world request/response examples.Pass
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Pass
Error-recovery guidanceDocumented failure modes and how to recover from them.Pass
Answer-first formatThe answer leads; preamble does not bury it.Pass
Capability boundariesClear limits — what the API can and cannot do.Pass
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Pass
Token efficiencyDocs are concise enough to fit an agent context window.Pass

What we found

  • An agent looking for Storybook would find it instantly: robots.txt explicitly allow-lists every major AI crawler (GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, and more), and both llms.txt and a 1.6MB llms-full.txt are present and comprehensive.
  • Best-in-class markdown access: appending `.md` to any docs URL returns clean LLM-ready markdown, with query params to filter by framework (`renderer`), language (`ts`/`js`), and code-only output — a level of agent-native content negotiation almost no other docs offer.
  • A canonical AGENTS.md lives in the primary storybookjs/storybook repo and explicitly designates itself as the source of truth for coding agents (CLAUDE.md points to it), plus an official first-party MCP server (@storybook/addon-mcp) with Claude Code and Codex plugins.
  • Comprehension is flawless (100/100): task-oriented docs, realistic multi-framework code examples, documented 'Known limitations', end-to-end tutorials, and actionable troubleshooting.
  • The only real gap is that Storybook exposes no OpenAPI/REST spec (it's a dev tool, not an HTTP service) and has no .well-known/mcp.json — both drag the Discovery score down even though neither is architecturally applicable.

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Add a `/.well-known/mcp.json` pointing to the official @storybook/addon-mcp server so agents can auto-discover the MCP endpoint without reading the addon README (quick win, +1 discovery weight).
  2. 02Publish a machine-readable spec for Storybook's public JS/CLI API surface (e.g. a JSON schema for CSF, main.ts config, and CLI options) so agents have a structured contract analogous to what OpenAPI provides for REST APIs.
  3. 03Cross-link the AGENTS.md and official MCP server directly from llms.txt so an agent that lands on llms.txt first is routed to the agent-specific tooling immediately.
  4. 04Consider a concise `llms.txt`-linked 'capabilities & limits' summary page so agents can grasp what Storybook can and cannot do without paging through the 1.6MB full dump.

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

✓ Error format documented✕ Rate limits documented✕ Pagination documented✕ Idempotency documented

Storybook is a local frontend dev tool, not an HTTP API, so most execution characteristics (auth, rate limits, pagination, idempotency) are N/A. Error handling is well documented: a dedicated `storybook doctor` command diagnoses common issues, and troubleshooting sections give concrete recovery steps.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free