Chrome Devtools MCP vs Pagerunner
A side-by-side look at the Chrome Devtools MCP and Pagerunner MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chrome Devtools MCP for browser automation work as a local process; choose Pagerunner for browser automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Chrome Devtools MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
click, drag, fill.
Choose Pagerunner when
- You need dedicated capabilities in the Browser Automation domain.
- You want tools like
list_profiles, open_session, attach_session.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 59/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 53,828 | 3 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 56 | 39 |
| Full listing | View Chrome Devtools MCP | View Pagerunner |
Tools & capabilities
Chrome Devtools MCP tools 56
clickdragfillfill_formhandle_dialoghoverpress_keytype_textupload_fileclick_atclose_pagelist_pages- +44 more on the listing page
Pagerunner tools 39
list_profilesList configured Chrome profilesopen_sessionLaunch Chrome for a profile, returns `session_idattach_sessionAttach to an existing Chrome instance via `--remote-debugging-portclose_sessionKill a Chrome sessionlist_sessionsList active sessionslist_tabsList open tabs in a sessionnew_tabOpen a new tab, returns `target_idclose_tabClose a specific tabnavigateNavigate a tab to a URLwait_forWait for a CSS selector, URL pattern, or fixed delayget_contentGet visible text content of a tabscreenshotCapture a tab as PNG (saved to temp file or inline base64)- +27 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Chrome Devtools MCP
{
"mcpServers": {
"chrome-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}
Pagerunner
No confirmed install command for Pagerunner yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Chrome Devtools MCP is categorized under Browser Automation and uses a local stdio subprocess. Pagerunner belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Chrome Devtools MCP for browser automation work and Pagerunner for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Pagerunner has no confirmed install command yet — follow its own setup instructions.
Chrome Devtools MCP is listed as free. Auth: no auth required. Pagerunner has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add chrome-devtools-mcp and pagerunner as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chrome Devtools MCP has a quality signal of 59/100 (Good) with 2 views, 0 installs and 53,828 GitHub stars. Pagerunner has 47/100 (Fair) with 0 views, 0 installs and 3 GitHub stars.