MCP Server
Clawbrowser exposes browser control through Model Context Protocol. Agents that support MCP can open pages, inspect state, click, type, capture screenshots, and continue work inside managed Clawbrowser profiles.
Install for your agent
Use clawctl to install Clawbrowser and wire the MCP server into the agent you use. The installer writes the local MCP configuration and validates the browser runtime.
clawctl install --agent claude-code --json
clawctl install --agent codex --json
clawctl install --agent all --jsonWhat the MCP server provides
The MCP server gives agents a stable tool interface for browser actions: navigation, screenshots, element interaction, tab control, profile startup, and session inspection.
The agent does not need to know how to connect to CDP directly. Clawbrowser keeps the browser identity, proxy, and fingerprint profile attached to the session.
When to use MCP vs CDP
Use MCP when the agent already supports tool calls and you want simple browser operations. Use CDP directly when your workflow is a custom Playwright, Puppeteer, or low-level automation script.