Log inSubmit server
Cws MCP logo

Cws MCP

by mikusnuz

Manage Chrome Web Store extension uploads, publishing, review status, staged rollouts, and dashboard listing fields through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Cws MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mikusnuz-cws-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cws-mcp"
      ],
      "env": {
        "CWS_CLIENT_ID": "YOUR_VALUE_HERE",
        "CWS_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "CWS_REFRESH_TOKEN": "YOUR_VALUE_HERE",
        "CWS_PUBLISHER_ID": "YOUR_VALUE_HERE",
        "CWS_ITEM_ID": "YOUR_VALUE_HERE",
        "CWS_DASHBOARD_PROFILE_DIR": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

mikusnuz/cws-mcp connects MCP clients to the Chrome Web Store for extension release management and selected dashboard listing updates. It uses Chrome Web Store API v2 for uploads, publishing, status checks, submission cancellation, and staged deployment percentages, while Playwright handles dashboard-based metadata workflows. Reach for it when an agent needs to upload an existing extension build, monitor review or deployment state, publish gradually, or update draft listing fields. New extension items still need to be created in the Developer Dashboard, and staged percentage deployment requires at least 10,000 seven-day active users.

Use cases

  • Upload a rebuilt ZIP as an existing extension draft
  • Publish an extension immediately or through staged deployment
  • Check review, upload, version, and rollout status
  • Cancel a submission that is under review
  • Update draft description, category, homepage, or support fields

Key features

  • Chrome Web Store API v2 release operations
  • Extension ZIP uploads for existing items
  • Immediate and staged publishing controls
  • Review and deployment status reporting
  • Dashboard-based listing metadata automation
  • Incremental staged rollout percentages

Tools8

What Cws MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 90d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · cws-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads314Package downloads in the last 30 days.
Last commit20d agoMost recent push to the default branch.
Tools exposed8Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Cws MCP works

What mikusnuz/cws-mcp does

mikusnuz/cws-mcp provides MCP tools for managing an existing Chrome Web Store extension through its release lifecycle. It can upload a ZIP as a draft, submit or publish an extension, inspect publication and upload state, cancel a pending submission, and raise the target percentage for a staged rollout.

The server also supports selected listing-field workflows through the Chrome Web Store dashboard. Dashboard automation can read or save the current draft description, category, homepage URL, and support URL. These changes do not submit the extension for review. Title, summary, default locale, icons, and screenshots follow other workflows: manifest or localized-message changes require a rebuilt ZIP, while visual assets are handled in the Developer Dashboard.

How it works

Chrome Web Store API v2 handles the release operations. After an upload, the result can remain asynchronous with an IN_PROGRESS state. The extension should be checked with status until lastAsyncUploadState becomes SUCCEEDED before publishing; a failed upload is returned as a tool error.

Publishing supports immediate or staged submission, an initial deployment percentage, skip-review behavior, and warning handling. STAGED_PUBLISH holds an approved submission for later publication; it is separate from the gradual rollout percentage. The deploy-percentage operation can only increase the current target and is restricted by Chrome Web Store eligibility requirements.

Metadata automation uses Playwright with a separate signed-in Chrome profile. It operates on the selected dashboard localization and current draft, rather than an arbitrary locale or the already-published listing. The server reports errors for missing fields, unmatched categories, ambiguous dashboard fields, and saves that cannot be verified.

Setup and configuration

Node.js 20 or newer is required. API access needs a Google Cloud project with the Chrome Web Store API enabled, OAuth2 desktop credentials, and a refresh token obtained through Google's desktop-app flow using PKCE, a local loopback redirect URI, offline access, and the Chrome Web Store scope.

Run the server directly with Node or through npx in an MCP client configuration. Required environment variables are CWS_CLIENT_ID, CWS_CLIENT_SECRET, and CWS_REFRESH_TOKEN. CWS_PUBLISHER_ID defaults to me, and CWS_ITEM_ID can provide a default extension ID. UI automation can use CWS_DASHBOARD_PROFILE_DIR, which defaults to ~/.cws-mcp-profile.

Google Chrome must be installed for dashboard operations. Use a non-headless first run when sign-in is needed, then reuse the browser profile. Select the intended dashboard localization before reading or saving fields.

Tools and capabilities

  • upload: Sends a ZIP for an existing item's draft.
  • publish: Submits or publishes with staged, rollout, skip-review, and warning controls.
  • status: Reports revision state, deployment percentage, version, warnings or takedown flags, and the latest upload state.
  • cancel: Withdraws a submission that is pending review.
  • deploy-percentage: Increases the target percentage for an eligible staged rollout.
  • get-metadata-ui and update-metadata-ui: Read or save supported listing fields through the dashboard.
  • get and update-metadata: Follow the current v2 and dashboard-based workflows described by the server version.

Limitations and notes

Creating a new Chrome Web Store item through the API is not supported; create it in the Developer Dashboard first. The deploy-percentage operation requires at least 10,000 seven-day active users, and each new percentage must exceed the current target.

The Chrome Web Store v1 API is deprecated and scheduled for removal after October 15, 2026. Published listing text is not exposed through the v2 status API. Dashboard automation can also require selector updates, so an unverified save should be checked in Chrome before retrying. The project is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Cws MCP

mikusnuz/cws-mcp is an MCP server that connects AI clients to the Chrome Web Store. Its main tools upload extension ZIPs, publish submissions, check status, cancel pending submissions, adjust staged rollout percentages, and update selected listing metadata through the Chrome dashboard.

Install it with Node.js 20 or newer and configure an MCP client to run the built entry point or `npx -y cws-mcp`. Add Google OAuth credentials and the required environment variables to the client configuration.

It requires `CWS_CLIENT_ID`, `CWS_CLIENT_SECRET`, and `CWS_REFRESH_TOKEN`. Create OAuth2 desktop credentials in Google Cloud, enable the Chrome Web Store API, and obtain a refresh token with the Chrome Web Store scope.

No, it can update and publish an existing item but cannot create new items through the API. Create the item first in the Chrome Web Store Developer Dashboard, then use the server to upload and manage its releases.

Use the dashboard metadata tools with a signed-in Chrome profile. They can read or save the current draft description, category, homepage URL, and support URL; select the intended localization first, and verify the dashboard when a save is ambiguous.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCws MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mikusnuz-cws-mcp?style=directory)](https://allmcps.com/mcp/mikusnuz-cws-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/mikusnuz-cws-mcp"><img src="https://allmcps.com/api/badge/mikusnuz-cws-mcp?style=directory" alt="Cws MCP on AllMCPs" /></a>