What is the key difference between Wopee MCP and Droidmind?

Wopee MCP belongs to the Browser Automation category with local stdio execution, while Droidmind belongs to the Browser Automation category with local stdio execution.

How do I install Wopee MCP or Droidmind 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 Wopee MCP and Droidmind free or paid?

Wopee MCP operates under a BYOK (Pay Provider Direct) model (API Key required). Droidmind operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Wopee MCP lists 9 tools with 2 views and 5 GitHub stars. Droidmind lists 6 tools with 2 views and 432 GitHub stars.

Can I use both Wopee MCP and Droidmind 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

Wopee MCP vs Droidmind

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

Wopee MCP

Browser Automation · Local stdio

Quality: 63/100 (Good) | Auth: API Key required

Droidmind

Browser Automation · Local stdio

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

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

Explore Wopee MCP Details

Choose Droidmind 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).
You have access to required keys: ANDROID_SERIAL, ADB_SERVER_SOCKET.
Primary tools included: Device connection and property inspection, System log access including logcat, ANR, crash, battery, File system browsing and file operations on device.

Feature & Specification Comparison

Specification	Wopee MCP Wopee-io Browser Automation	Droidmind hyperb1iss Browser Automation
Summary	Autonomous testing for web apps — dispatch AI agents that open real browsers, execute test cases, and report pass/fail with screenshots. Generate user stories, test cases, and Playwright code from your app context. 8 tools for end-to-end test automation.	Control Android devices with AI through MCP, enabling device control, debugging, system analysis, and UI automation with a comprehensive security framework.
Category & Scope

Tools & Capabilities Breakdown

Wopee MCP Tools (9)

wopee_fetch_analysis_suites

Fetches all analysis suites for your project. This is a good starting point to see what suites are available.

wopee_dispatch_analysis

Creates and dispatches a new analysis/crawling suite for your project, or reruns an existing one. Use this to start a fresh analysis session or to re-trigger a previous analysis.

wopee_create_blank_suite

Creates a blank analysis suite for your project. Use this when you want to manually configure and populate a suite rather than having it automatically analyzed.

wopee_generate_artifact

Generates a specific file(artifact) for the selected suite.

wopee_fetch_artifact

Fetches the enquired file(artifact) from the selected suite.

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).

Wopee MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "wopee-io-wopee-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "wopee-mcp"
      ],
      "env": {
        "WOPEE_PROJECT_UUID": "YOUR_WOPEE_PROJECT_UUID_HERE",
        "WOPEE_API_KEY": "YOUR_WOPEE_API_KEY_HERE"
      }
    }
  }
}

Droidmind Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "hyperb1iss-droidmind": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/hyperb1iss/droidmind",
        "droidmind",
        "--transport",
        "stdio"
      ],
      "env": {
        "ANDROID_SERIAL": "YOUR_ANDROID_SERIAL_HERE",
        "ADB_SERVER_SOCKET": "YOUR_ADB_SERVER_SOCKET_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Wopee MCP More alternatives to Droidmind Browser Automation category hub Canonical compare URL