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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago