Log inSubmit server

ShotAPI vs Chrome Devtools MCP

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

ShotAPI logoShotAPIBrowser AutomationScreenshot and HTML rendering MCP server for AI agents28EmergingAuth: not declaredChrome Devtools MCP logoChrome Devtools MCPBrowser Automation · Local subprocess (stdio)Chrome DevTools for coding agents65GreatAuth: no auth required

Verdict: choose ShotAPI for browser automation work; choose Chrome Devtools MCP 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?

ShotAPI logoChoose ShotAPI when

  • You need dedicated capabilities in the Browser Automation domain.
  • You have the keys it needs: SHOTAPI_BASE_URL, SHOTAPI_KEY.
Explore ShotAPI

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecShotAPI logoShotAPIChrome Devtools MCP logoChrome Devtools MCP
CategoryBrowser AutomationBrowser Automation
Quality signal28/100 · Emerging65/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsSHOTAPI_BASE_URLSHOTAPI_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars153,996
Directory activity 2 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listed56
Full listingView ShotAPI View Chrome Devtools MCP

Tools & capabilities

ShotAPI tools

No tool names declared yet. Check the project README from the listing page.

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

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.

ShotAPI

No confirmed install command for ShotAPI yet — follow the setup steps linked from its listing page rather than a guessed package name.

Chrome Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}

Frequently asked questions

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

ShotAPI has no declared pricing — check the project's own site. Chrome Devtools MCP is listed as free. Auth: no auth required. 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 shotapi and chrome-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, ShotAPI has a quality signal of 28/100 (Emerging) with 2 views, 0 installs and 1 GitHub stars. Chrome Devtools MCP has 65/100 (Great) with 6 views, 0 installs and 53,996 GitHub stars.

Popular comparisons with ShotAPI

Popular comparisons with Chrome Devtools MCP