MCP-native browser runtime
MCP browser control for agents that need a real browser.
Vessel is an open-source AI agent browser built for Model Context Protocol workflows. It gives agents a durable Chromium surface they can operate while humans supervise what is happening.
Why MCP needs a browser runtime
LLM agents can call tools, but web work often needs more than one-off HTTP requests. Real workflows need cookies, visible pages, local state, tab continuity, screenshots, and human override. Vessel gives MCP clients a persistent browser they can inhabit instead of a disposable headless session.
Persistent sessionsKeep cookies, localStorage, tabs, and workflow context across restarts.
Human-supervised controlThe agent acts in a visible browser surface so a human can audit, steer, or stop work.
Local-first runtimeRun browser automation on your own machine instead of routing every session through a cloud browser API.
Agent-oriented primitivesPage diffing, state tracking, and durable context are designed around autonomous web work.
Best fit
- Research agents that need durable browser state.
- Local open-model workflows that need web access.
- Human-in-the-loop browser automation.
- MCP clients that need a visible Chromium runtime.
Search phrase version: if you need an MCP browser, a browser for AI agents, or a local open-source alternative to cloud browser automation, Vessel is built for that exact job.