mikusnuz/cws-mcp

한국어
MCP server for Chrome Web Store extension management. Upload, publish, and manage Chrome extensions directly from Claude Code or any MCP client.
When to Use
Use this MCP when you need to:
- **"Upload a new version of my Chrome extension"** — build your ZIP and use the upload tool to push it as a draft
- **"Publish my extension to the Chrome Web Store"** — use publish to submit for review and go live
- **"Check the review status of my extension"** — use status to see review state, version, and deploy percentage
- **"Update my extension's description or category"** — use update-metadata to save and verify the draft listing
- **"Cancel a pending submission"** — use cancel to withdraw a submission under review
- **"Set up staged rollout for my extension"** — use publish with staged rollout, then deploy-percentage to ramp up
Tools
| Tool | Description |
|---|---|
| upload | Upload a ZIP file to Chrome Web Store (update existing item draft) |
| publish | Submit/publish with publish type, rollout percentage, skip-review, and blockOnWarnings |
| status | Fetch the current status including review state, deploy percentage, and version |
| cancel | Cancel a pending submission |
| deploy-percentage | Set staged rollout percentage (0-100, must exceed current target) |
| get | Alias of status: v2 publication status, not listing text |
| get-metadata-ui | Read the current draft description, category, homepage URL, and support URL from the dashboard |
| update-metadata | Save those four supported draft fields through the dashboard and verify them after reload |
| update-metadata-ui | Alias of update-metadata |
API Coverage
This MCP server covers **all Chrome Web Store API v2 endpoints**:
| v2 Endpoint | MCP Tool |
|---|---|
| media.upload | upload |
| publishers.items.publish | publish |
| publishers.items.fetchStatus | status |
| publishers.items.cancelSubmission | cancel |
| publishers.items.setPublishedDeployPercentage | deploy-percentage |
All API requests use v2. The public API has no listing-text read/write endpoints; dashboard tools use Playwright and a separate signed-in Chrome profile. Saving listing fields never submits for review. Missing fields, unmatched categories, and unconfirmed saves return errors instead of success.
Setup
1. Create OAuth2 Credentials
1. Go to Google Cloud Console
2. Create a project (or select existing)
3. Enable **Chrome Web Store API**
4. Create OAuth2 credentials (Desktop app type)
5. Note your **Client ID** and **Client Secret**
2. Get Refresh Token
Follow Google's OAuth flow for desktop apps using a local loopback redirect URI, PKCE, and the scope https://www.googleapis.com/auth/chromewebstore. Request offline access (access_type=offline; use prompt=consent when you need a new refresh token). Exchange the authorization code using the same redirect URI and keep the refresh token in your MCP client's secret/environment settings. The former copy-and-paste OOB redirect is no longer supported by Google.
3. Configure MCP
Add to your Claude Code MCP settings (~/.claude/settings.local.json):
Or install globally via npm:
Environment Variables
| Variable | Required | Description |