Web To Mcp

Created By
Web-To-MCP8 months ago
Bridge the gap between design and code. Send pixel-perfect website components directly to Cursor or Claude Code using Model Context Protocol (MCP). No more screenshots or descriptions needed.
Overview

what is Web To Mcp?

Web To Mcp is a tool that bridges the gap between design and code by allowing users to send pixel-perfect website components directly to AI coding assistants like Cursor or Claude Code using the Model Context Protocol (MCP).

how to use Web To Mcp?

To use Web To Mcp, install the Chrome extension, select a UI component from a live website, and receive a reference ID. Paste this ID into your IDE chat with Cursor or Claude to fetch the component's HTML, CSS, typography, colors, spacing, and layout context.

key features of Web To Mcp?

  • Capture real UI components from live websites.
  • Receive exact DOM structure and consolidated CSS.
  • Get computed styles for sizing, spacing, fonts, and colors.
  • Small preview images for quick visual checks.
  • Clean output compatible with React, Vue, Angular, or plain HTML/CSS.

use cases of Web To Mcp?

  1. Designers can quickly grab examples of UI components.
  2. Developers can obtain accurate code for implementation.
  3. Teams can reduce the handoff time from trial-and-error to minutes, ensuring UI matches the original design.

FAQ from Web To Mcp?

  • Is Web To Mcp free to use?

Yes! Web To Mcp is free to use for everyone.

  • What browsers are supported?

Currently, Web To Mcp supports the Chrome browser through its extension.

  • Can I use Web To Mcp with any website?

Yes! You can capture components from any live website.

Server Config

{
  "mcpServers": {
    "web-to-mcp": {
      "url": "https://web-to-mcp.com/mcp/<YOUR_UNIQUE_ID>"
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
Web-To-MCP
Star
-
Language
-
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