What is the key difference between Currents MCP and Wopee MCP?

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

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

Currents MCP operates under a BYOK (Pay Provider Direct) model (API Key required). Wopee MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Currents MCP lists 40 tools with 3 views and 20 GitHub stars. Wopee MCP lists 9 tools with 2 views and 5 GitHub stars.

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

Currents MCP vs Wopee MCP

In-depth architectural comparison of the Currents 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

Currents MCP

Browser Automation · Local stdio

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

Wopee MCP

Browser Automation · Local stdio

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

Verdict Summary: Choose Currents 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 Currents 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: CURRENTS_API_KEY.
Primary tools included: currents-list-actions, currents-create-action, currents-get-action.

Explore Currents MCP Details

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

Feature & Specification Comparison

Specification	Currents MCP currents-dev Browser Automation	Wopee MCP Wopee-io Browser Automation
Summary	Enable AI Agents to fix Playwright test failures reported to Currents.	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.
Category & Scope	Browser Automation

Tools & Capabilities Breakdown

Currents MCP Tools (40)

currents-list-actions

List all actions for a project with optional filtering.

currents-create-action

Create a new action for a project.

currents-get-action

Get a single action by ID.

currents-update-action

Update an existing action.

currents-delete-action

Delete (archive) an action.

currents-enable-action

Enable a disabled action.

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

Currents MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "currents-dev-currents-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@currents/mcp"
      ],
      "env": {
        "CURRENTS_API_KEY": "YOUR_CURRENTS_API_KEY_HERE"
      }
    }
  }
}

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"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Currents MCP More alternatives to Wopee MCP Browser Automation category hub