cws-mcp
MCP server for Chrome Web Store extension management. Upload, publish, and manage Chrome extensions directly from Claude Code or any MCP client.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y [email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
CWS_CLIENT_ID=<secret> CWS_CLIENT_SECRET=<secret> CWS_REFRESH_TOKEN=<secret> claude mcp add mikusnuz-cws-mcp -- npx -y cws-mcp@2.0.2在終端機中執行。
{ "mcpServers": { "mikusnuz-cws-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "CWS_CLIENT_ID": "<secret>", "CWS_CLIENT_SECRET": "<secret>", "CWS_REFRESH_TOKEN": "<secret>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
MCP server for Chrome Web Store extension management. Upload, publish, and manage Chrome extensions directly from Claude Code or any MCP client.
MCP server for Chrome Web Store — upload, publish, status, metadata & Playwright-based UI automation
Use this MCP when you need to:
upload tool to push it as a draftpublish to submit for review and go livestatus to see review state, version, and deploy percentageupdate-metadata to save and verify the draft listingcancel to withdraw a submission under reviewpublish with staged rollout, then deploy-percentage to ramp upAn 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:
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.
Requires Node.js 20 or newer, matching the Playwright runtime requirement.
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.
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": { ... }
}
}
}
Use the cws-mcp status tool
1. Use cws-mcp upload with zipPath="/path/to/extension.zip"
2. Use cws-mcp publish
Use cws-mcp publish with:
- publishType="STAGED_PUBLISH"
Use cws-mcp publish with skipReview=true
STAGED_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.
Use cws-mcp publish with blockOnWarnings=true
The default is false, matching the API. Inspect returned warningInfo.warnings even when publishing succeeds.
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:
category must match the visible option label exactly in the current dashboard language; English and Korean field labels are supported.manifest.json / localized messages, rebuild, and upload the ZIP. Use the dashboard directly for icons and screenshots.headless=false if login is required.~/.cws-mcp-profile (override with CWS_DASHBOARD_PROFILE_DIR).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=100
Note: 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.
Google shuts down API v1 on October 15, 2026. Version 2.0 no longer calls it:
get now returns v2 status. Its old projection argument is rejected; use get-metadata-ui for draft listing text. Published listing text is not exposed by v2.update-metadata now uses the same dashboard workflow as update-metadata-ui and therefore needs Chrome login, not just an API token.metadata, title, summary, and defaultLocale inputs are rejected with guidance; unsupported inputs are never silently ignored.storeIconPath is 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.MIT
MCP server for Chrome Web Store — upload, publish, status, metadata & Playwright-based UI automation
{ "mcpServers": { "mikusnuz-cws-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "CWS_CLIENT_ID": "<secret>", "CWS_CLIENT_SECRET": "<secret>", "CWS_REFRESH_TOKEN": "<secret>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN。
Cws 透過 stdio 在本機執行。
上次檢查時間:2026-10-28。 MCP server for Chrome Web Store — upload, publish, status, metadata & Playwright-based UI automation