What is the key difference between Jevnav and Vibe Test — Browser Testing Agent?

Jevnav belongs to the Browser Automation category with local stdio execution, while Vibe Test — Browser Testing Agent belongs to the Browser Automation category with local stdio execution.

How do I install Jevnav or Vibe Test — Browser Testing Agent in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Jevnav and Vibe Test — Browser Testing Agent free or paid?

Jevnav operates under a Free / Open Source model (No auth required). Vibe Test — Browser Testing Agent operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Jevnav lists 6 tools with 0 views and 2 GitHub stars. Vibe Test — Browser Testing Agent lists 14 tools with 0 views and 5 GitHub stars.

Can I use both Jevnav and Vibe Test — Browser Testing Agent together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Jevnav vs Vibe Test — Browser Testing Agent

In-depth architectural comparison of the Jevnav and Vibe Test — Browser Testing Agent 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.

At a Glance & Executive Verdict

Jevnav

Browser Automation · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Vibe Test — Browser Testing Agent

Browser Automation · Local stdio

Quality: 53/100 (Good) | Auth: No auth required

Verdict Summary: Choose Jevnav if you need specialized Browser Automation tools running via a local process. Choose Vibe Test — Browser Testing Agent if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Jevnav 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).
You have access to required keys: TYPESAFE_API_KEY.
Primary tools included: Intent-based element selection with Jev, Confidence and risk gates, Auditable JSONL session traces.

Explore Jevnav Details

Choose Vibe Test — Browser Testing Agent 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: configure, scan_codebase, get_context.

Feature & Specification Comparison

Specification	Jevnav Browser Automation	Vibe Test — Browser Testing Agent Browser Automation
Summary	Replayable browser automation: Jev picks the element, a gate blocks risky actions, every run traces.	Code-aware browser testing agent — 13 Playwright tools for AI code editors via MCP
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

Jevnav Tools (6)

Intent-based element selection with Jev

Confidence and risk gates

Auditable JSONL session traces

Offline replay and success verification

Page outlines, styles, and control inspection

Mockup-to-application UI diffing

Vibe Test — Browser Testing Agent Tools (14)

configure

Structured setup result and idempotent project files

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

Jevnav Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "jevnav": {
      "command": "uvx",
      "args": [
        "jevnav"
      ],
      "env": {
        "TYPESAFE_API_KEY": "YOUR_TYPESAFE_API_KEY_HERE"
      }
    }
  }
}

Vibe Test — Browser Testing Agent Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vibe-test-browser-testing-agent": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing@latest"
      ]
    }
  }
}

Frequently Asked Questions

Jevnav is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Vibe Test — Browser Testing Agent belongs to Browser Automation using local stdio subprocess. Select Jevnav when you need capabilities focused on browser automation and Vibe Test — Browser Testing Agent when you require tools for browser automation.

More alternatives to Jevnav More alternatives to Vibe Test — Browser Testing Agent Browser Automation category hub