Shotanvil vs MCP Server Browser

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

Shotanvil logoShotanvilBrowser Automation · Remote HTTP/SSEScreenshot/PDF/HTML rendering API. API key or x402 required — keyless access disabled.37FairAuth: not declaredMCP Server Browser logoMCP Server BrowserBrowser Automation · Local subprocess (stdio)Browser automation capabilities using Puppeteer, both support local and remote browser connection.67GreatAuth: no auth required

Verdict: choose Shotanvil for browser automation work over a hosted endpoint; choose MCP Server Browser 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?

Shotanvil logoChoose Shotanvil when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: SHOTANVIL_API_KEY.
Explore Shotanvil

MCP Server Browser logoChoose MCP Server Browser 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 browser_click, browser_close, browser_close_tab.
Explore MCP Server Browser

Feature & specification comparison

Rows where the two servers differ are marked.

SpecShotanvil logoShotanvilMCP Server Browser logoMCP Server Browser
CategoryBrowser AutomationBrowser Automation
Quality signal37/100 · Fair67/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsSHOTANVIL_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars039,368
Directory activity 1 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listed23

Tools & capabilities

Shotanvil tools

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

MCP Server Browser tools 23

  • browser_clickClick an element on the page, before using the tool, use `browser_get_clickable_elements` to get the index of the element, but not call `browser_get_clickable_elements` multiple times
  • browser_closeClose the browser when the task is done and the browser is not needed anymore
  • browser_close_tabClose the current tab
  • browser_evaluateExecute JavaScript in the browser console
  • browser_form_input_fillFill out an input field, before using the tool, Either 'index' or 'selector' must be provided
  • browser_get_clickable_elementsGet the clickable or hoverable or selectable elements on the current page, don't call this tool multiple times
  • browser_get_download_listGet the list of downloaded files
  • browser_get_markdownGet the markdown content of the current page
  • browser_get_textGet the text content of the current page
  • browser_go_backGo back to the previous page
  • browser_go_forwardGo forward to the next page
  • browser_hoverHover an element on the page, Either 'index' or 'selector' must be provided
  • +11 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.

Shotanvil

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shotanvil": {
      "url": "https://api.shotanvil.com"
    }
  }
}

MCP Server Browser

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-infra-mcp-server-browser": {
      "command": "npx",
      "args": [
        "-y",
        "@agent-infra/mcp-server-browser"
      ]
    }
  }
}

Frequently asked questions

Shotanvil is categorized under Browser Automation and uses a remote HTTP/SSE transport. MCP Server Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Shotanvil for browser automation work and MCP Server Browser 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.

Shotanvil has no declared pricing — check the project's own site. MCP Server Browser 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 shotanvil and agent-infra-mcp-server-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Shotanvil has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. MCP Server Browser has 67/100 (Great) with 6 views, 0 installs and 39,368 GitHub stars.