# mikusnuz/cws-mcp [Health: Active]

**Category:** 📂 Browser Automation  
**Repository:** https://github.com/mikusnuz/cws-mcp  
**GitHub Stars:** 4  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mikusnuz-cws-mcp

## Description
MCP server for Chrome Web Store extension management — 8 tools for upload, publish, status, staged rollout, and metadata updates.

## Tools
Capabilities this server exposes over MCP:

- **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.
- **get** — Get the current metadata of a Chrome Web Store item (v1.1 API). Returns title, description, category, and other listing fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026.
- **update-metadata** — Update the store listing metadata of a Chrome Web Store item (v1.1 API). Supports both common fields and raw metadata payload for advanced fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026. Use update-metadata-ui as an alternative.
- **update-metadata-ui** — Update listing metadata via Chrome Web Store dashboard UI automation (Playwright). Use this when API metadata updates are not reflected, or as the primary metadata update method since the v1 API is deprecated.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "cws-mcp": {
    "command": "npx",
    "args": ["-y","cws-mcp"],
    "env": {
      "CWS_CLIENT_ID": "",
      "CWS_CLIENT_SECRET": "",
      "CWS_REFRESH_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `CWS_CLIENT_ID`, `CWS_CLIENT_SECRET`, `CWS_REFRESH_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What mikusnuz/cws-mcp MCP server does

The mikusnuz/cws-mcp MCP server exposes eight MCP tools for managing existing Chrome Web Store extension listings. It covers the release lifecycle: uploading a ZIP as a draft, submitting or publishing a release, checking its state, withdrawing a pending submission, and increasing the audience during a staged rollout. It also provides tools for reading and changing store listing metadata.

New Chrome Web Store items cannot be created through the supported v2 API flow described here. An item must first exist in the Developer Dashboard, after which the server can work with its extension ID. The upload operation updates an existing item draft rather than creating a listing.

## How it works

Most operations use the Chrome Web Store API with Google OAuth2 credentials. The server requires a client ID, client secret, and refresh token, and can use a publisher ID and item ID as defaults. The v2-backed tools cover media upload, publishing, status retrieval, submission cancellation, and published deployment percentage changes.

Publishing supports immediate or staged release modes, an initial deployment percentage, and an option to skip review. After a staged release, the deployment percentage tool can raise the target in steps. Each new percentage must be greater than the current target, and Google limits this feature to items with at least 10,000 seven-day active users.

Metadata operations have two paths. The `get` and `update-metadata` tools use the Chrome Web Store v1.1 API. The `update-metadata-ui` tool instead automates the store dashboard with Playwright, which is useful when API changes are not reflected or when the dashboard is the preferred long-term route.

## Setup and configuration

Install the mikusnuz/cws-mcp MCP server through npm with `npx -y cws-mcp`, then register it in the MCP client configuration. The documented configuration runs the package through Node-compatible npm execution and supplies credentials as environment variables.

Create a Google Cloud project, enable the Chrome Web Store API, and create OAuth2 credentials for a desktop application. Obtain a refresh token using the Chrome Web Store OAuth scope. The required variables are `CWS_CLIENT_ID`, `CWS_CLIENT_SECRET`, and `CWS_REFRESH_TOKEN`. `CWS_PUBLISHER_ID` defaults to `me`, while `CWS_ITEM_ID` can provide a default extension identifier.

Dashboard automation uses the browser profile configured by `CWS_DASHBOARD_PROFILE_DIR`. Its default location is `~/.cws-mcp-profile`. If login is needed, the documented workflow is to run the UI operation with headless mode disabled first so the profile can be authenticated.

## Tools and capabilities

- `upload`: Uploads a ZIP to an existing item draft.
- `publish`: Submits or publishes an extension, including staged publishing options.
- `status`: Reports review state, version, deployment percentage, warnings, takedown flags, and upload state.
- `cancel`: Withdraws a pending submission.
- `deploy-percentage`: Raises the target audience percentage for an eligible staged rollout.
- `get`: Reads listing metadata through the deprecated v1.1 API.
- `update-metadata`: Writes common or raw metadata through the deprecated v1.1 API.
- `update-metadata-ui`: Changes listing fields through Playwright dashboard automation.

## Limitations and notes

The mikusnuz/cws-mcp MCP server does not create new Chrome Web Store items through its v2 API coverage. The v1.1 metadata endpoints used by `get` and `update-metadata` are deprecated and scheduled for removal after October 15, 2026; the dashboard automation tool is the stated alternative. Staged deployment percentage changes must move upward and require the documented active-user threshold. The project is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/mikusnuz-cws-mcp/readme_