cws-mcp
Summary: cws-mcp is an MCP server for managing Chrome Web Store extensions — uploading ZIPs, publishing, checking status, canceling submissions, and editing store listing metadata.
Upload a new draft:
uploadpushes a ZIP to an existing item draft (no new-item creation via API).Publish:
publishsubmits for review withpublishType(DEFAULT_PUBLISH/STAGED_PUBLISH), optionaldeployPercentage, andskipReview.Check status:
statusreturns review state, revision, version, deploy percentage, takedown/warning flags, and last upload state.Cancel a submission:
cancelwithdraws an item currently under review.Staged rollout:
deploy-percentagesets a higher rollout target (requires 10,000+ weekly active users).Read listing metadata:
getfetches item metadata (title, description, category, etc.) with DRAFT/PUBLISHED projection.Update listing metadata:
update-metadata/update-metadata-uiset description, category, homepage URL, support URL (and more via API/raw metadata), with UI automation for unreflected fields.Configure defaults:
itemIdandpublisherIdfall back toCWS_ITEM_ID/CWS_PUBLISHER_IDenv vars; UI tool supportsheadlessandaccountIndexoptions.
Enables management of Chrome Web Store extensions, allowing users to upload ZIP files, publish versions with optional staged rollouts, check review status, and update store listing metadata.
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
uploadtool to push it as a draft"Publish my extension to the Chrome Web Store" — use
publishto submit for review and go live"Check the review status of my extension" — use
statusto see review state, version, and deploy percentage"Update my extension's description or category" — use
update-metadatato save and verify the draft listing"Cancel a pending submission" — use
cancelto withdraw a submission under review"Set up staged rollout for my extension" — use
publishwith staged rollout, thendeploy-percentageto ramp up
Related MCP server: browser-mcp
Tools
Tool | Description |
| Upload a ZIP file to Chrome Web Store (update existing item draft) |
| Submit/publish with publish type, rollout percentage, skip-review, and |
| Fetch the current status including review state, deploy percentage, and version |
| Cancel a pending submission |
| Set staged rollout percentage (0-100, must exceed current target) |
| Alias of |
| Read the current draft description, category, homepage URL, and support URL from the dashboard |
| Save those four supported draft fields through the dashboard and verify them after reload |
| Alias of |
API Coverage
An upload returning IN_PROGRESS is pending: poll status until lastAsyncUploadState is SUCCEEDED before publishing. FAILED is a tool error. A blocked publish retains error.details, including the warnings that need attention.
This MCP server covers all Chrome Web Store API v2 endpoints:
v2 Endpoint | MCP Tool |
|
|
|
|
|
|
|
|
|
|
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
Requires Node.js 20 or newer, matching the Playwright runtime requirement.
1. Create OAuth2 Credentials
Go to Google Cloud Console
Create a project (or select existing)
Enable Chrome Web Store API
Create OAuth2 credentials (Desktop app type)
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):
{
"mcpServers": {
"cws-mcp": {
"command": "node",
"args": ["/path/to/cws-mcp/dist/index.js"],
"env": {
"CWS_CLIENT_ID": "xxxxx.apps.googleusercontent.com",
"CWS_CLIENT_SECRET": "GOCSPX-xxxxx",
"CWS_REFRESH_TOKEN": "1//xxxxx",
"CWS_PUBLISHER_ID": "me",
"CWS_ITEM_ID": "your-extension-id"
}
}
}
}Or install globally via npm:
{
"mcpServers": {
"cws-mcp": {
"command": "npx",
"args": ["-y", "cws-mcp"],
"env": { ... }
}
}
}Environment Variables
Variable | Required | Description |
| Yes | Google OAuth2 Client ID |
| Yes | Google OAuth2 Client Secret |
| Yes | OAuth2 Refresh Token |
| No | Publisher ID (default: |
| No | Default extension item ID |
| No | Browser profile path for UI automation (default: |
Usage Examples
Check extension status
Use the cws-mcp status toolUpload and publish
1. Use cws-mcp upload with zipPath="/path/to/extension.zip"
2. Use cws-mcp publishHold publication until after approval
Use cws-mcp publish with:
- publishType="STAGED_PUBLISH"Publish with skip-review
Use cws-mcp publish with skipReview=trueSTAGED_PUBLISH holds an approved submission for a later publication; it is not the rollout percentage. Use deployPercentage separately for an eligible extension's gradual rollout.
Stop publishing on validation warnings
Use cws-mcp publish with blockOnWarnings=trueThe default is false, matching the API. Inspect returned warningInfo.warnings even when publishing succeeds.
Read or save listing fields without submitting for review
Use cws-mcp get-metadata-ui with headless=false
Use cws-mcp update-metadata with:
- description="..."
- category="Developer Tools"
- homepageUrl="https://example.com"
- supportUrl="https://example.com/support"Notes:
categorymust match the visible option label exactly in the current dashboard language; English and Korean field labels are supported.These tools read/save the current dashboard draft, not the published listing or an arbitrary locale. Select the intended localization in the dashboard first; ambiguous fields fail safely.
Change title, summary, and default locale in
manifest.json/ localized messages, rebuild, anduploadthe ZIP. Use the dashboard directly for icons and screenshots.First run with
headless=falseif login is required.Browser profile path defaults to
~/.cws-mcp-profile(override withCWS_DASHBOARD_PROFILE_DIR).Google Chrome must be installed. Dashboard UI changes can require selector updates; unverified saves return errors. Verify the dashboard before retrying an ambiguous failure.
Staged rollout
1. Use cws-mcp publish with deployPercentage=10
2. Monitor approval/publication with status
3. Use cws-mcp deploy-percentage with percentage=50
4. Use cws-mcp deploy-percentage with percentage=100Note: deploy-percentage is only available for extensions with 10,000+ seven-day active users. The new percentage must always be higher than the current target.
Migrating from 1.x to 2.0
Google shuts down API v1 on October 15, 2026. Version 2.0 no longer calls it:
getnow returns v2 status. Its oldprojectionargument is rejected; useget-metadata-uifor draft listing text. Published listing text is not exposed by v2.update-metadatanow uses the same dashboard workflow asupdate-metadata-uiand therefore needs Chrome login, not just an API token.Raw
metadata,title,summary, anddefaultLocaleinputs are rejected with guidance; unsupported inputs are never silently ignored.storeIconPathis no longer accepted as a working upload. The previous generic file-input approach could not verify which asset it changed; upload the icon in the Developer Dashboard instead.
License
MIT
Available Tools
9 toolscancelA
Cancel a pending submission on Chrome Web Store. Can be used to cancel an item currently in review.
Inputs: itemId, publisherId.
deploy-percentageA
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.
Inputs: percentage (required), itemId, publisherId.
getA
Fetch publication status through v2 (alias of status). Version 2 no longer returns listing metadata or supports projection; use get-metadata-ui for draft listing text.
Inputs: itemId, projection, publisherId.
get-metadata-uiA
Read the current draft listing description, category, homepage and support URL from the signed-in Developer Dashboard. This is not the published listing.
Inputs: itemId, headless, accountIndex.
publishC
Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.
Inputs: itemId, skipReview, publishType, publisherId, +2 more.
statusA
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.
Inputs: itemId, publisherId.
update-metadataA
Save draft listing description, category, homepage or support URL via the signed-in Developer Dashboard, then reload to verify. Does not submit for review. Package title/summary, raw payloads, and icon uploads are unsupported.
Inputs: title, itemId, summary, category, +8 more.
update-metadata-uiA
Save draft listing description, category, homepage or support URL via the signed-in Developer Dashboard, then reload to verify. Does not submit for review. Package title/summary, raw payloads, and icon uploads are unsupported.
Inputs: title, itemId, summary, category, +8 more.
uploadA
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.
Inputs: zipPath (required), itemId, publisherId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Two pairs of tools are near-duplicates: 'update-metadata' and 'update-metadata-ui' share identical descriptions, and 'get' is explicitly documented as an alias of 'status'. An agent has no reliable basis for choosing between the members of each pair, though the remaining tools (upload, publish, cancel, deploy-percentage) are distinguishable.
All names use kebab-case, but the verb styles vary: bare imperatives (publish, cancel, upload, get), a noun (status), a noun phrase (deploy-percentage), and compound action names (update-metadata-ui, get-metadata-ui). The '-ui' suffix convention appears meaningful but is applied inconsistently since the non-'-ui' variant has the same description.
Nine tools is a reasonable scope for a Chrome Web Store publishing workflow. The count is slightly inflated by two redundant/aliased tools that could be collapsed.
The core lifecycle (upload, publish, status, cancel, staged rollout, metadata draft) is covered, but notable gaps remain: no item creation, no published-listing metadata read (only drafts via the dashboard), no icon/package title edits, and no takedown operation. Some gaps reflect API v2 limits, but agents will hit dead ends.
Maintenance
Related MCP Connectors
Unofficial Browserless MCP — wraps the Browserless headless-Chromium REST API (browserless.io)
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
MCP server for Mint — AI-powered QA that runs your app in a real browser on every PR.
Hosted MCP for YouTube Studio: uploads, metadata, playlists, comments, analytics, captions.
Related MCP Servers
- AlicenseBqualityDmaintenanceA universal browser automation MCP server using Playwright, enabling programmatic control of Chrome with 63 tools for navigation, interaction, media control, and CDP-based diagnostics.6313 npm3MIT
- AlicenseNot gradedqualityCmaintenanceUnified MCP server for browser automation (Playwright + CDP + CLI) and bookmark management across Chrome, Firefox, Edge, and Brave, including cross-browser sync, deduplication, and a React dashboard.1MIT
- AlicenseAqualityDmaintenanceMCP server for Chrome extension testing. Access chrome.storage, Service Workers, declarativeNetRequest, and more directly from AI coding agents like Claude Code.231MIT
- FlicenseAqualityDmaintenanceEnterprise web automation testing MCP server that controls local Chrome via Playwright CDP, providing tools for page element analysis, interaction, dynamic layer exploration, VTable scene graph, test recording, and Shadcn-style Excel export.24-