Log inSubmit server

Chrome Devtools MCP vs Screenshot

A side-by-side look at the Chrome Devtools MCP and Screenshot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Chrome Devtools MCP logoChrome Devtools MCPBrowser Automation · Local subprocess (stdio)Chrome DevTools for coding agents65GreatAuth: no auth required
S
ScreenshotBrowser AutomationScreenshot any URL/HTML as PNG/JPEG/WebP, or read it as clean Markdown/text for LLMs.12EmergingAuth: not declared

Verdict: choose Chrome Devtools MCP for browser automation work as a local process; choose Screenshot for browser automation. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Chrome Devtools MCP logoChoose 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.
Explore Chrome Devtools MCP

S
Choose Screenshot when

  • You need dedicated capabilities in the Browser Automation domain.
Explore Screenshot

Feature & specification comparison

Rows where the two servers differ are marked.

SpecChrome Devtools MCP logoChrome Devtools MCP
S
Screenshot
CategoryBrowser AutomationBrowser Automation
Quality signal65/100 · Great12/100 · Emerging
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars54,008—
Directory activity 6 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools56Not listed
Full listingView Chrome Devtools MCP View Screenshot

Tools & capabilities

Chrome Devtools MCP tools 56

  • click
  • drag
  • fill
  • fill_form
  • handle_dialog
  • hover
  • press_key
  • type_text
  • upload_file
  • click_at
  • close_page
  • list_pages
  • +44 more on the listing page

Screenshot tools

No tool names declared yet. Check the project README from 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}

Screenshot

No confirmed install command for Screenshot 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. Screenshot belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Chrome Devtools MCP for browser automation work and Screenshot 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. Screenshot has no confirmed install command yet — follow its own setup instructions.

Chrome Devtools MCP is listed as free. Auth: no auth required. Screenshot 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 screenshot 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 6 views, 0 installs and 54,008 GitHub stars. Screenshot has 12/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars.

Popular comparisons with Chrome Devtools MCP

Popular comparisons with Screenshot