Cws MCP

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.