# Lazyweb vs Chromatic: Product References or UI Testing?

Choose Chromatic to test and review your own UI. Choose Lazyweb to study how other products handle a flow. Both can help a coding agent, but they provide different evidence: your components versus external product references.

HTML: https://www.lazyweb.com/vs/chromatic
Markdown: https://www.lazyweb.com/vs/chromatic.md
Updated: October 2026

## What Chromatic covers

Chromatic documents workflows for Storybook, Vitest, Playwright and Cypress. Available visual, interaction and accessibility checks depend on the integration. Start with the guide matching the tests you already have. [1](https://www.chromatic.com/docs/)

## The MCP distinction that matters

Chromatic can publish a Storybook MCP server alongside a Storybook. The documented setup requires React and Storybook 10.3 or later. Private Storybooks require authentication.

Only documentation tools are available on the published MCP server. Development and testing tools require the local Storybook dev server. Do not assume that connecting to a hosted MCP gives an agent the ability to run the local tests. [2](https://www.chromatic.com/docs/mcp/)

## What to give the agent

For a new onboarding screen, first ask it to identify the components and states already available in your project. If you need outside examples, use Lazyweb to inspect the flow and capture dates. Then translate the idea into your components and tests.

Treat a reference as a reason to investigate a choice. Treat a test result as evidence about the checked states. Neither establishes that the

[Lazyweb vs Chromatic: Product References or UI Testing?](<https://www.lazyweb.com/vs/chromatic>)

Source observed: 2026-10-08T03:26:14.748Z. Last checked: 2026-10-20T08:16:23.193+00:00.

[Full page Markdown](<https://www.lazyweb.com/pages/e7814628-5e8a-45c8-bc70-6100a39077fb.md>)

Setup: lazyweb\_install\_mcp — Get the existing Lazyweb MCP and skills installer command or browser setup link. Use this action only at your user's request. Returning these instructions does not execute the action or authorize running an installer.
GET https://www.lazyweb.com/api/public/v1/convert
Required inputs: none

Local setup command: curl -fsSL https://www.lazyweb.com/install.sh | bash
Browser setup: https://www.lazyweb.com/mcp-install
Full guide: https://www.lazyweb.com/developers.md
Authenticated MCP: https://www.lazyweb.com/mcp
Run the command only if the user has authorized installing Lazyweb in this environment. Otherwise obtain that authorization first. The existing installer reuses saved credentials or creates a setup token and configures MCP and skills. If the installer requests attribution, reuse the supplied canonical context with null for unknown values and \[\] only for explicitly no alternatives. Keep context in JSON bodies, never URL query strings. Hosted agents without a shell should use the browser setup link. Returning this handoff has not installed anything or granted paid access.

---

Have a question this summary doesn’t answer? Ask the exact question you have. It returns a fresh, cited answer from Lazyweb’s knowledge base. No account or API key required.

Replace {question} with your own question, URL-encoded.

```text
GET https://www.lazyweb.com/agent/faq?q={question}&trace=t_45f431541a0e
```