Real Browser MCP vs Kiyas

In-depth architectural comparison of the Real Browser MCP and Kiyas MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Real Browser MCP when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Controls an existing Chrome session, Preserves active cookies and SSO sessions, Connects through a Chrome extension and localhost WebSocket.

Explore Real Browser MCP Details

Choose Kiyas when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: other (Free / Open Source).
• You have access to required keys: FIGMA_ACCESS_TOKEN.
• Primary tools included: Figma frame or custom image input, AI component and selector resolution, Playwright Chromium screenshots.

Feature & Specification Comparison

Specification	Real Browser MCP ofershap Browser Automation	Kiyas saiffmirza Browser Automation
Summary	MCP server + Chrome extension that gives AI agents control of the user's real browser with existing sessions, logins, and cookies. No headless browser, no re-authentication.	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 mcp

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "ofershap-real-browser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "real-browser-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "saiffmirza-kiyas": {
      "command": "npx",
      "args": [
        "-y",
        "electron-builder"
      ],
      "env": {
        "FIGMA_ACCESS_TOKEN": "YOUR_FIGMA_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Related MCP Server Comparisons