Chrome Devtools MCP vs Plasmate
A side-by-side look at the Chrome Devtools MCP and Plasmate 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 Plasmate for browser automation as a local process. 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 Plasmate when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
fetch_page, extract_text, open_page.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 65/100 · Great | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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,900 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 56 | 6 |
| Full listing | View Chrome Devtools MCP | View Plasmate |
Tools & capabilities
Chrome Devtools MCP tools 56
clickdragfillfill_formhandle_dialoghoverpress_keytype_textupload_fileclick_atclose_pagelist_pages- +44 more on the listing page
Plasmate tools 6
fetch_pageFetch a URL and get the Semantic Object Model (SOM)extract_textGet clean readable text from any URLopen_pageOpen a persistent browser sessionclickClick elements by SOM IDevaluateExecute JavaScript in the pageclose_pageClose a browser session
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"
]
}
}
}
Plasmate
{
"mcpServers": {
"plasmate-2": {
"command": "npx",
"args": [
"-y",
"plasmate-mcp"
]
}
}
}
Frequently asked questions
Chrome Devtools MCP is categorized under Browser Automation and uses a local stdio subprocess. Plasmate belongs to Browser Automation and uses a local stdio subprocess. Pick Chrome Devtools MCP for browser automation work and Plasmate 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.
Chrome Devtools MCP is listed as free. Auth: no auth required. Plasmate 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 plasmate-2 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 65/100 (Great) with 5 views, 0 installs and 53,900 GitHub stars. Plasmate has 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars.