Jev Browser vs Playwright MCP Server
A side-by-side look at the Jev Browser and Playwright MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
J
Jev BrowserBrowser Automation · Local subprocess (stdio)Browser automation where an LLM plans and Jev (Typesafe System One) makes every per-step decision. Library, CLI and MCP server.52GoodAuth: api key requiredVerdict: choose Jev Browser for browser automation work as a local process; choose Playwright MCP Server 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?
JChoose Jev Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TYPESAFE_API_KEY, OPENROUTER_API_KEY, JEV_API_URL, JEV_MODEL, JEV_BROWSER_HEADED.
Choose Playwright MCP Server 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
start_codegen_session, end_codegen_session, get_codegen_session.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | J Jev Browser | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 52/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | TYPESAFE_API_KEYOPENROUTER_API_KEYJEV_API_URLJEV_MODELJEV_BROWSER_HEADED | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 122 | 5,664 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 33 |
| Full listing | View Jev Browser | View Playwright MCP Server |
Tools & capabilities
Jev Browser tools
No tool names declared yet. Check the project README from the listing page.
Playwright MCP Server tools 33
start_codegen_sessionStart a new code generation session to record Playwright actionsend_codegen_sessionEnd a code generation session and generate the test fileget_codegen_sessionGet information about a code generation sessionclear_codegen_sessionClear a code generation session without generating a testplaywright_navigateNavigate to a URLplaywright_screenshotTake a screenshot of the current page or a specific elementplaywright_clickClick an element on the pageplaywright_iframe_clickClick an element in an iframe on the pageplaywright_iframe_fillFill an element in an iframe on the pageplaywright_fillfill out an input fieldplaywright_selectSelect an element on the page with Select tagplaywright_hoverHover an element on the page- +21 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.
Jev Browser
{
"mcpServers": {
"jev-browser": {
"command": "npx",
"args": [
"-y",
"-p",
"jev-browser",
"jev-browser-mcp"
],
"env": {
"TYPESAFE_API_KEY": "YOUR_TYPESAFE_API_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
"JEV_API_URL": "YOUR_JEV_API_URL_HERE",
"JEV_MODEL": "YOUR_JEV_MODEL_HERE",
"JEV_BROWSER_HEADED": "YOUR_JEV_BROWSER_HEADED_HERE"
}
}
}
}
Playwright MCP Server
{
"mcpServers": {
"executeautomation-playwright-mcp-server": {
"command": "npx",
"args": [
"-y",
"@executeautomation/playwright-mcp-server"
]
}
}
}
Frequently asked questions
Jev Browser is categorized under Browser Automation and uses a local stdio subprocess. Playwright MCP Server belongs to Browser Automation and uses a local stdio subprocess. Pick Jev Browser for browser automation work and Playwright MCP Server 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.
Jev Browser is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Playwright MCP Server 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 jev-browser and executeautomation-playwright-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jev Browser has a quality signal of 52/100 (Good) with 0 views, 0 installs and 122 GitHub stars. Playwright MCP Server has 67/100 (Great) with 2 views, 0 installs and 5,664 GitHub stars.
