Side-by-Side Model Context Protocol Comparison
Wavexis MCP vs Wopee MCP
In-depth architectural comparison of the Wavexis MCP and Wopee 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
Wavexis MCP
Browser Automation · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Wopee MCP
Browser Automation · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Wavexis MCP if you need specialized Browser Automation tools running via a local process. Choose Wopee 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 Wavexis MCP 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: wavexis_session_open, wavexis_session_close, wavexis_session_info.
Choose Wopee MCP 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:
WOPEE_PROJECT_UUID, WOPEE_API_KEY. - Primary tools included: wopee_fetch_analysis_suites, wopee_dispatch_analysis, wopee_create_blank_suite.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Wavexis MCP Tools (72)
wavexis_session_open
Launch a persistent browser session for multi-step workflows.
Call once at the start of a task and reuse the returned session_id for
all subsequent calls; use wavexis_navigate with session_id omitted for
one-off page fetches instead.
Side effects: Launches a browser process (or connects to an existing
one) and allocates server-side session state; may open network
connections to remote/cloud browsers.
Returns: JSON string with keys: 'status' ('ok'/'error'),
'session_id' (str), 'backend' (str).
wavexis_session_close
Close a browser session and release all associated resources.
Call when the session is no longer needed to free memory and browser
processes; use wavexis_close_tab to close individual tabs instead.
Side effects: Terminates the browser process (or disconnects from a
remote one) and frees session state. Destructive — all unsaved page
state is lost.
Returns: JSON string with keys: 'status' ('ok'/'error'),
'session_id' (str).
wavexis_session_info
Query metadata and current URL of an active browser session.
Use to inspect session health or retrieve the current page URL; use
wavexis_list_tabs for tab-level details instead.
Side effects: None — read-only; queries in-memory session state and
the browser's current URL.
Returns: JSON string with keys: 'status' ('ok'/'error'),
'session_id' (str), 'backend' (str), 'created_at' (str),
'current_url' (str).
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).
Wavexis MCP Configuration
Wopee MCP Configuration