Frane Vibesurfer

frane/vibesurfer·1 plugin

Add this marketplace when your coding agent needs a real headless browser over MCP with stateful primitives instead of brittle curl-only checks.

Overview

frane-vibesurfer is a plugin marketplace for the Build phase that supplies MCP-driven headless real-browser automation through the vibesurfer (vs) plugin.

What is this marketplace?

Headless real browser via WKWebView, WebKitGTK, or WebView2—not a mocked DOM.
20 primitives, state-token concurrency, tree deltas, audit-by-construction design.
MCP-tagged plugin; requires `vs` on PATH (Homebrew tap frane/tap or README curl installer).
Unix-socket wire protocol suited to scripted agent loops and repeatable UI flows.
Marketplace lists 1 plugin with 20 browser primitives and state-token concurrency
Plugin tags include browser, headless, webkit, stateful, mcp, automation

Compatible agents: Claude Code, Cursor, Codex, any compatible agent

What problem does it solve?

Agents cannot reliably interact with modern web UIs using fetch-only tools or fake DOM stubs.

Who is it for?

Solo builders automating login flows, SPAs, or WebView-heavy apps from Claude Code via MCP.

Skip if: Builders who only need static HTML scraping without a local browser binary, or teams blocked from installing native CLI tools.

What do I get? / Deliverables

After registering the marketplace and installing `vs`, your agent can drive a stateful headless browser with twenty wire-protocol primitives for integration and flow testing.

vibesurfer plugin wired into your agent MCP surface
Runnable headless browser automation using 20 documented primitives

Plugins in this marketplace

1 plugin — install individually after you add the marketplace.

PluginVersion

VibesurferHeadless real browser (WKWebView/WebKitGTK/WebView2) driven over a Unix-socket wire protocol. 20 primitives, state-token concurrency, tree deltas, audit-by-construction. Requires the `vs` binary on PATH (install via `brew tap frane/tap && brew install vibesurfer` or the curl one-liner from the README).—

Recommended Marketplaces

Acanilcancakir/claude-code

Anilcan Cakir's ac marketplace packages two complementary Claude Code plugins for builders who want more discipline arou…

Acbc Codeacbcdev/claude-code

acbc-code is a three-plugin Claude Code marketplace from acbcdev aimed at solo builders who want agent help across git h…

Agent Accordsdaniloc/agent-accords

agent-accords is a Claude Code plugin marketplace from Agent Accords that ships one plugin, how-to-build-software, packa…

Agent Harness Pluginscboone/agent-harness-plugins

agent-harness-plugins is a large Claude Code marketplace listing fifty-one small plugins aimed at developers building co…2 stars

Agentic Codingffalor/agentic-coding

agentic-coding is a Claude Code plugin marketplace by ffalor that packages ten plugins for indie developers practicing a…

Agent MarketplaceMrMYHuang/agent-marketplace

agent-marketplace is a small, curated Claude and VS Code chat plugin marketplace for solo builders who want ready-made a…

Journey fit

Primary fit

BuildIntegrations & version control

Browser automation is primarily a build-time integration for agents that must drive real WebKit/Chromium surfaces during development and verification. Integrations subphase covers MCP servers and external runtimes; vibesurfer is an agent-native browser wire protocol behind the vs binary.

How it compares

MCP browser integration marketplace, not a frontend component orchestrator or slide generator.

Common Questions / FAQ

Who is Frane Vibesurfer for?

Developers using MCP-enabled coding agents who need real browser automation during build and test workflows.

When should I use Frane Vibesurfer?

Use it when integrating agent-driven UI checks, scripted navigation, or stateful browser sessions on macOS/Linux/Windows WebView stacks.

How do I add Frane Vibesurfer to my agent?

Register market:frane/vibesurfer in Claude Code, install the vibesurfer plugin, then install the `vs` binary with `brew tap frane/tap && brew install vibesurfer` or the README curl one-liner and confirm it is on PATH.