In-depth architectural comparison of the Browser Use MCP Server and Cws MCP 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
Browser Use MCP Server
Browser Automation · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Cws MCP
Browser Automation · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Browser Use MCP Server if you need specialized Browser Automation tools running via a local process. Choose Cws MCP 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 Browser Use MCP Server when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: OPENAI_API_KEY, CHROME_PATH, PATIENT.
Primary tools included: Browser control through browser-use, SSE and stdio transport modes, Asynchronous browser operations.
Upload a ZIP file to update an existing Chrome Web Store item draft. Note: Creating new items via API is not supported in v2 — use the Developer Dashboard to create new items.
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).
Browser Use MCP Server is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Cws MCP belongs to Browser Automation using local stdio subprocess. Select Browser Use MCP Server when you need capabilities focused on browser automation and Cws MCP when you require tools for browser automation.
Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.
status
Fetch the current status of an extension on Chrome Web Store. Returns published/submitted revision status, deploy percentage, version, takedown/warning flags, and last upload state.
cancel
Cancel a pending submission on Chrome Web Store. Can be used to cancel an item currently in review.
deploy-percentage
Set the published deploy percentage for staged rollout on Chrome Web Store. The new percentage must be higher than the current target. Only available for items with 10,000+ seven-day active users.
get
Get the current metadata of a Chrome Web Store item (v1.1 API). Returns title, description, category, and other listing fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026.
update-metadata
Update the store listing metadata of a Chrome Web Store item (v1.1 API). Supports both common fields and raw metadata payload for advanced fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026. Use update-metadata-ui as an alternative.
update-metadata-ui
Update listing metadata via Chrome Web Store dashboard UI automation (Playwright). Use this when API metadata updates are not reflected, or as the primary metadata update method since the v1 API is deprecated.