MCP Server Browser vs Kiyas

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

MCP Server Browser logoMCP Server BrowserBrowser Automation · Local subprocess (stdio)Browser automation capabilities using Puppeteer, both support local and remote browser connection.67GreatAuth: no auth requiredKiyas logoKiyasBrowser Automation · Local subprocess (stdio)Design-fidelity checks for AI agents: compare a Figma frame (or any design screenshot) against the rendered implementation and get structured discrepancies with CSS properties and severity. Resolves a natural-language component description to a URL + selector in your codebase, screenshots it with Playwright, and compares via vision AI using your existing Claude Code or Codex subscription — no API keys. 90% mutation recall, zero false positives on its golden eval set. npx -y kiyas-cli mcp59GoodAuth: other

Verdict: choose MCP Server Browser for browser automation work as a local process; choose Kiyas 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?

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

Kiyas logoChoose Kiyas when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You have the keys it needs: FIGMA_ACCESS_TOKEN.
Explore Kiyas

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Browser logoMCP Server BrowserKiyas logoKiyas
CategoryBrowser AutomationBrowser Automation
Quality signal67/100 · Great59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredother
PricingFreeFree
Required env varsNone listedFIGMA_ACCESS_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars39,3681
Directory activity 6 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools23Not listed

Tools & capabilities

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

Kiyas 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.

MCP Server Browser

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

Kiyas

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "saiffmirza-kiyas": {
      "command": "npx",
      "args": [
        "-y",
        "electron-builder"
      ],
      "env": {
        "FIGMA_ACCESS_TOKEN": "YOUR_FIGMA_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

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

MCP Server Browser is listed as free. Auth: no auth required. Kiyas is listed as free. Auth: other. 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 agent-infra-mcp-server-browser and saiffmirza-kiyas as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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