agent-browser adds an MCP server

Introduced 2026-06-16 · score 0.99

HOW TO USE IT

When exposing agent-browser automation to an MCP client, start the stdio server with `agent-browser mcp`; use the default `core` profile or select `all` or comma-separated profiles with `--tools`.

WHY THIS HELPS

Expose browser automation tools to an MCP client.

REQUIREMENTS AND LIMITATIONS

• Version: v0.28.0
• --tools: Select MCP tool profiles; defaults to `core`. `all` selects every MCP tool; comma-separated profile names compose profiles. The docs do not state that profiles are mutually exclusive.
• core: Default profile: navigation, snapshots, interaction, waits, reads, screenshots, JavaScript eval, close, tab basics, and profile discovery.
• network: Profile for network routes, request inspection, HAR, headers, credentials, and offline controls.
• state: Profile for cookies, storage, auth, saved state, sessions, profiles, and skills.
• debug: Profile for console/errors, tracing, profiling, recording, clipboard, plugins, doctor, dashboard, install, upgrade, chat, diff, batch, and confirm/deny.
• tabs: Profile for back/forward/reload, tabs, windows, frames, and dialogs.
• react: Profile for React tree/inspect/renders/suspense, vitals, and pushstate.
• mobile: Profile for viewport/device/geolocation/media, touch, swipe, mouse, and keyboard.
• all: Every MCP tool, including the full typed CLI parity surface.
• Prerequisite: Configure the MCP client to launch command `agent-browser` with args `["mcp"]`; the server communicates over stdio.
• The server uses stdio.
• The default `core` profile keeps context small.

FIRST-PARTY EVIDENCE

• https://github.com/vercel-labs/agent-browser/releases/tag/v0.28.0
• https://github.com/vercel-labs/agent-browser/blob/v0.28.0/skill-data/core/references/commands.md

Check the installed version and the source before using it. Entry JSON

Report a problem with this card