Skip to main content
Glama
matipojo

simple-storybook-preview-mcp

by matipojo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to simple-storybook-preview-mcp

No user-submitted related servers found.

    Related Servers

    • storybook-mcp

      stevebrownlee
      A
      license
      A
      quality
      D
      maintenance
      Integrates with a running Storybook instance to let AI-powered coding tools browse, inspect, and scaffold components from natural language.
      4
      25 PyPI
      MIT

    • msw-mcp

      ploy6318
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to dynamically add, update, and remove Mock Service Worker network mocks through MCP tools, including scaffolding project setup. Changes take effect in the running browser app without restarting the application source code.
      15 npm
      MIT

    • msw-mcp

      Eriksson451
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to dynamically add, update, and remove Mock Service Worker network mocks through MCP tools, using a WebSocket bridge to live browser sessions and a setup prompt that scaffolds the MSW integration. Changes apply without restarting the application or editing its source.
      15 npm
      MIT

    • msw-mcp

      rmendoza05484
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to dynamically add, update, and remove Mock Service Worker network mocks via MCP tools, with a browser bridge that applies changes without restarting the application.
      15 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool there is no possibility of confusion or overlap with other tools. The single purpose of rendering a Storybook story is clearly defined.

    Naming Consistency5/5

    The tool name 'render_component' follows a clear verb_noun pattern, which is consistent and predictable. Even as a lone tool, the naming convention is clear and readable.

    Tool Count3/5

    A single tool for a very narrow 'simple storybook preview' purpose is borderline. It is not trivial, but the surface feels thin and lacks supplementary functionality that might be expected in a fuller server.

    Completeness4/5

    The tool fully covers the core rendering action, and the convention-based storyId allows agents to target stories. A notable gap is the absence of a discovery mechanism to list available stories or validate storyIds, but for a 'simple' preview server this is a minor limitation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources