Cms vs Browser Use
A side-by-side look at the Cms and Browser Use MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cms for browser automation work; choose Browser Use 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 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Cms | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 37/100 · Fair | 45/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 118,881 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Cms | View Browser Use |
Tools & capabilities
Cms tools
No tool names declared yet. Check the project README from the listing page.
Browser Use 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.
Cms
No confirmed install command for Cms yet — follow the setup steps linked from its listing page rather than a guessed package name.
Browser Use
{
"mcpServers": {
"browser-use": {
"command": "uvx",
"args": [
"browser-use"
]
}
}
}
