mcp-design-system-extractor

Created By
freemaa year ago
MCP (Model Context Protocol) server that enables AI assistants to interact with Storybook design systems. Extract component HTML, analyze styles, and help with design system adoption and refactoring.
Overview

what is MCP Design System Extractor?

MCP Design System Extractor is a server that enables AI assistants to interact with Storybook design systems, allowing for the extraction of component HTML and analysis of styles to facilitate design system adoption and refactoring.

how to use MCP Design System Extractor?

To use the MCP Design System Extractor, set up the server and connect it to your Storybook design system. The server will then allow you to extract HTML components and analyze their styles.

key features of MCP Design System Extractor?

  • Extracts component HTML from Storybook design systems
  • Analyzes styles for better design system adoption
  • Assists in refactoring design systems for improved usability

use cases of MCP Design System Extractor?

  1. Streamlining the integration of design systems into projects.
  2. Facilitating the refactoring of existing design systems for better performance.
  3. Enhancing collaboration between design and development teams through better component management.

FAQ from MCP Design System Extractor?

  • Can MCP Design System Extractor work with any design system?

Yes! It is designed to work with Storybook design systems but can be adapted for others.

  • Is there a cost associated with using MCP Design System Extractor?

No, it is open-source and free to use under the MIT license.

  • How do I contribute to the MCP Design System Extractor?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
freema
Star
0
Language
-
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago