Chrome Devtools MCP vs Periscope MCP
A side-by-side look at the Chrome Devtools MCP and Periscope MCP 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 Periscope MCP 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 Periscope MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You want tools like
create_project, list_projects, get_project.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 59/100 · Good | 48/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 | 10 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 56 | 74 |
| Full listing | View Chrome Devtools MCP | View Periscope MCP |
Tools & capabilities
Chrome Devtools MCP tools 56
clickdragfillfill_formhandle_dialoghoverpress_keytype_textupload_fileclick_atclose_pagelist_pages- +44 more on the listing page
Periscope MCP tools 74
create_projectCreate a new testing projectlist_projectsList all projectsget_projectGet project detailsdelete_projectDelete project + dataset_form_loginConfigure username/password form loginset_basic_authConfigure HTTP Basic Authset_cookiesInject session cookieslogin_projectExecute login using configured authinteractive_loginOpen a **visible** window to log in by hand (2FA/SSO/CAPTCHA), then `save_loginsave_loginCapture the manual-login session; the project then runs authenticated + headlesscopy_authCopy auth config + session state between projectstest_urlTest a single URL (screenshot + checks)- +62 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"
]
}
}
}
Periscope MCP
No confirmed install command for Periscope MCP 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. Periscope MCP belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Chrome Devtools MCP for browser automation work and Periscope MCP 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. Periscope MCP has no confirmed install command yet — follow its own setup instructions.
Chrome Devtools MCP is listed as free. Auth: no auth required. Periscope MCP 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 segentic-lab-periscope-mcp 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. Periscope MCP has 48/100 (Fair) with 1 views, 0 installs and 10 GitHub stars.
