What is the key difference between Wavexis MCP and Devloop?

Wavexis MCP belongs to the Browser Automation category with local stdio execution, while Devloop belongs to the Browser Automation category with local stdio execution.

How do I install Wavexis MCP or Devloop in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Wavexis MCP and Devloop free or paid?

Wavexis MCP operates under a Free / Open Source model (No auth required). Devloop operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Wavexis MCP lists 72 tools with 4 views and 1 GitHub stars. Devloop lists 68 tools with 2 views and 2 GitHub stars.

Can I use both Wavexis MCP and Devloop together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Wavexis MCP vs Devloop

In-depth architectural comparison of the Wavexis MCP and Devloop 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

Devloop

Browser Automation · Local stdio

Quality: 61/100 (Good) | Auth: No auth required

Verdict Summary: Choose Wavexis MCP if you need specialized Browser Automation tools running via a local process. Choose Devloop 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.

Explore Wavexis MCP Details

Choose Devloop 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: project, cmd, cwd.

Explore Devloop Details

Feature & Specification Comparison

Specification	Wavexis MCP MathiasPaulenko Browser Automation	Devloop vincentvella Browser Automation
Summary	MCP server exposing 220 browser automation tools across 13 capability tiers. Chrome + Firefox via CDP + BiDi. No Node.js, no Chromium download — uses your existing browser. Stealth mode, Lighthouse audits, multi-action YAML batching, raw CDP/BiDi access, structured errors with LLM-actionable suggestions.	Drives a browser (or a native Expo/React Native app on iOS/Android) and your dev server onto one correlated timeline, so a browser console error and the backend stack trace from the same moment line up. Includes repro action sequences, a unified log/network query API, and an Electron cockpit.
Category & Scope

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

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mathiaspaulenko-wavexis-mcp": {
      "command": "uvx",
      "args": [
        "wavexis-mcp"
      ]
    }
  }
}

Devloop Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vincentvella-devloop": {
      "command": "npx",
      "args": [
        "-y",
        "devloop-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Wavexis MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Devloop belongs to Browser Automation using local stdio subprocess. Select Wavexis MCP when you need capabilities focused on browser automation and Devloop when you require tools for browser automation.

More alternatives to Wavexis MCP More alternatives to Devloop Browser Automation category hub