V0.dev Response Capture Tool

Created By
m2radsa year ago
MCP Server to connect your MCP host to V0.dev directly
Overview

what is v0-mcp?

v0-mcp is a browser automation script that utilizes Playwright to connect your existing Chrome browser to the v0.dev website, preserving all your accounts and cookies.

how to use v0-mcp?

To use v0-mcp, you can either connect to your existing Chrome browser with remote debugging enabled or let the script handle everything by launching Chrome automatically.

key features of v0-mcp?

  • Connects to your existing Chrome browser with all your accounts/cookies.
  • Creates a new tab to navigate to v0.dev.
  • Falls back to launching Chrome with your profile if not already running.
  • Keeps your Chrome instance open after the script finishes.

use cases of v0-mcp?

  1. Automating the opening of v0.dev in a new tab without losing session data.
  2. Simplifying browser automation tasks for developers using Playwright.
  3. Enhancing productivity by maintaining user sessions while automating web interactions.

FAQ from v0-mcp?

  • What are the prerequisites for using v0-mcp?

You need Python 3.8+ and Google Chrome installed on your machine.

  • How do I install Playwright?

You can install Playwright using pip with the command: pip install playwright.

  • What if I encounter issues while running the script?

Try closing all Chrome instances and rerun the script, or ensure that Chrome is launched with remote debugging enabled.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
m2rads
Star
2
Language
Python
License
-
Tags

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