What crawlio-browser MCP server does
The crawlio-browser MCP server gives an MCP client control of a live Chrome tab rather than launching a separate browser process. It is suited to pages whose useful content appears only after JavaScript runs, including single-page applications and authenticated sites. The agent can work with the selected tab’s existing session, cookies, and page state.
Tab management tools can list open tabs, connect by URL or tab ID, disconnect, reconnect, and report connection or permission status. Once connected, the agent can navigate pages, interact with controls, inspect rendered content, and collect browser diagnostics.
How it works
The MCP server runs as a Node.js process and communicates with the Crawlio Chrome extension over WebSocket. The extension uses Chrome DevTools Protocol to operate the browser.
The normal flow is:
- Install the Chrome extension.
- Start the MCP server with the initialization wizard or a client configuration.
- Connect the agent to a browser tab.
- Use browser, capture, and inspection tools against that tab.
The server supports stdio transport for clients that manage the process lifecycle. Portal mode provides a local Streamable HTTP endpoint at http://127.0.0.1:3001/mcp, while SSE mode is available for clients that require that transport. Portal mode is intended for sessions that should survive client restarts or context compaction.
Setup and configuration
Install the package and run the initialization wizard:
The wizard can configure supported MCP clients and offers options for full tool exposure, portal mode, dry runs, and noninteractive installation. Run npx crawlio-browser tools to inspect the default tool surface, or add --full for the individually exposed tools. doctor checks the bridge, portal, native host, and client configurations without requiring a browser connection.
Manual stdio configuration uses the installed package through npx -y crawlio-browser. For portal mode, start npx crawlio-browser --portal and configure the client with the local MCP URL. The package also includes an Agent Plugins v1 layout, but it must be installed with its dependencies rather than run from an unpacked archive.
Tools and capabilities
The crawlio-browser MCP server includes tools for:
- Navigating, clicking, double-clicking, typing, hovering, selecting options, scrolling, dragging, uploading files, pressing keys, and waiting for page states.
- Capturing a page’s framework information, network activity, console output, and DOM.
- Detecting JavaScript frameworks and versions, reading console logs, inspecting cookies with sensitive values redacted, and retrieving captured response bodies.
- Taking viewport, full-page, or element screenshots in JPEG or PNG format.
- Starting and stopping network recording, intercepting URL patterns, mocking or modifying responses, emulating offline or preset network conditions, and toggling the browser cache.
The browser bridge also reports live availability by tab, CDP domain, and permission state. Framework-aware behavior is described in the project documentation, but the directly listed tools above are the concrete interface covered here.
Limitations and notes
The crawlio-browser MCP server only operates on a tab after the agent connects one. Connecting Chrome’s debugger gives the agent access to content and browser state for that session, including logged-in sites; review the selected tab and consider using a dedicated Chrome profile. The extension honors pages that opt out with <meta name="crawlio-agent" content="disable">.
A live Chrome installation and the Crawlio extension are required for browser operations. The tools and doctor commands can inspect configuration or expose the tool list without a browser, extension, or network connection. The supplied tool list describes 147 CDP tools, while the README also refers to broader modes and additional capabilities, so verify the exposed surface with the local CLI before depending on a particular mode.