What is the key difference between Cws MCP and Real Browser MCP?

Cws MCP belongs to the Browser Automation category with local stdio execution, while Real Browser MCP belongs to the Browser Automation category with local stdio execution.

How do I install Cws MCP or Real Browser 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 Cws MCP and Real Browser MCP free or paid?

Cws MCP operates under a Free / Open Source model (OAuth 2.0). Real Browser MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Cws MCP lists 8 tools with 3 views and 4 GitHub stars. Real Browser MCP lists 6 tools with 3 views and 50 GitHub stars.

Can I use both Cws MCP and Real Browser 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

Cws MCP vs Real Browser MCP

In-depth architectural comparison of the Cws MCP and Real Browser 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

Cws MCP

Browser Automation · Local stdio

Quality: 59/100 (Good) | Auth: OAuth 2.0

Real Browser MCP

Browser Automation · Local stdio

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

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

You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN.
Primary tools included: upload, publish, status.

Explore Cws MCP Details

Choose Real Browser 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: Controls an existing Chrome session, Preserves active cookies and SSO sessions, Connects through a Chrome extension and localhost WebSocket.

Feature & Specification Comparison

Specification	Cws MCP mikusnuz Browser Automation	Real Browser MCP ofershap Browser Automation
Summary	MCP server for Chrome Web Store extension management — 8 tools for upload, publish, status, staged rollout, and metadata updates.	MCP server + Chrome extension that gives AI agents control of the user's real browser with existing sessions, logins, and cookies. No headless browser, no re-authentication.
Category & Scope	Browser Automation

Tools & Capabilities Breakdown

Cws MCP Tools (8)

upload

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.

publish

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.

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

Cws MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mikusnuz-cws-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cws-mcp"
      ],
      "env": {
        "CWS_CLIENT_ID": "YOUR_CWS_CLIENT_ID_HERE",
        "CWS_CLIENT_SECRET": "YOUR_CWS_CLIENT_SECRET_HERE",
        "CWS_REFRESH_TOKEN": "YOUR_CWS_REFRESH_TOKEN_HERE"
      }
    }
  }
}

Real Browser MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ofershap-real-browser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "real-browser-mcp"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Cws MCP More alternatives to Real Browser MCP Browser Automation category hub