Browser Use MCP Server vs Jev Browser
A side-by-side look at the Browser Use MCP Server and Jev Browser 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.59GoodAuth: api key requiredVerdict: choose Browser Use MCP Server for browser automation work over a hosted endpoint; choose Jev 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?
Choose Browser Use MCP Server when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, CHROME_PATH, PATIENT.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | J Jev Browser | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 55/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | OPENAI_API_KEYCHROME_PATHPATIENT | TYPESAFE_API_KEYOPENROUTER_API_KEYJEV_API_URLJEV_MODELJEV_BROWSER_HEADED |
| Verified owner | Community listing | Community listing |
| GitHub stars | 847 | 123 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Browser Use MCP Server | View Jev Browser |
Tools & capabilities
Browser Use MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Jev Browser 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.
Browser Use MCP Server
{
"mcpServers": {
"co-browser-browser-use-mcp-server": {
"url": "http://localhost:8000/sse"
}
}
}
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"
}
}
}
}
Frequently asked questions
Browser Use MCP Server is categorized under Browser Automation and uses a remote HTTP/SSE transport. Jev Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Browser Use MCP Server for browser automation work and Jev 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.
Browser Use MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Jev Browser is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 co-browser-browser-use-mcp-server and jev-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser Use MCP Server has a quality signal of 55/100 (Good) with 5 views, 0 installs and 847 GitHub stars. Jev Browser has 59/100 (Good) with 0 views, 0 installs and 123 GitHub stars.
