Brand-to-Theme MCP Server

Created By
mmokarzela year ago
Servidor MCP para convertir PDFs de identidad de marca en temas de Shopify
Overview

What is Brand-to-Theme MCP Server?

Brand-to-Theme MCP Server is a tool designed to convert brand identity PDFs into functional Shopify themes, ensuring consistency with brand identity.

How to use Brand-to-Theme MCP Server?

To use the server, clone the repository, install dependencies, and configure the MCP server. You can then extract branding elements from a PDF, generate design tokens, create a Shopify theme, and install it directly into your Shopify store.

Key features of Brand-to-Theme MCP Server?

  • PDF Extraction: Analyzes PDFs to extract color palettes, typography, and other design elements.
  • Design Tokens Generation: Converts extracted elements into standardized design tokens.
  • Shopify Theme Creation: Generates complete theme files based on brand identity.
  • Shopify Integration: Allows direct installation of the theme into the connected store.
  • Figma Integration: Compatible with components extracted from Figma.

Use cases of Brand-to-Theme MCP Server?

  1. Automating the conversion of brand manuals into Shopify themes.
  2. Ensuring brand consistency across online stores.
  3. Streamlining the theme creation process for Shopify developers.

FAQ from Brand-to-Theme MCP Server?

  • Can this server convert any PDF?

It is designed to work with brand identity PDFs that contain the necessary design elements.

  • Is there a cost to use this server?

The server is open-source and free to use.

  • What are the system requirements?

Node.js v16+ and a Shopify Partner Account are required.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mmokarzel
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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