
Cws
- 3 repo stars
- Updated April 13, 2026
- mikusnuz/cws-mcp
Lets an AI agent upload, publish, check status of, and stage rollout for a Chrome extension via the Chrome Web Store API without the CWS dashboard.
About
Chrome Web Store MCP is a Model Context Protocol server that drives the Chrome Web Store publishing API from an AI agent. It handles uploading an extension package, publishing it, checking review/publish status, and managing a staged rollout, using Google OAuth2 credentials. A solo builder reaches for it at launch to ship or update a Chrome extension and control its rollout without clicking through the Chrome Web Store developer dashboard.
- Upload extension packages to the Chrome Web Store
- Publish and check review status
- Staged percentage rollout
- OAuth2-authenticated CWS API access
Cws by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env CWS_CLIENT_ID=YOUR_CWS_CLIENT_ID --env CWS_CLIENT_SECRET=YOUR_CWS_CLIENT_SECRET --env CWS_REFRESH_TOKEN=YOUR_CWS_REFRESH_TOKEN cws-mcp -- npx -y cws-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 3 |
|---|---|
| Package | cws-mcp |
| Transport | STDIO |
| Auth | Required |
| Last updated | April 13, 2026 |
| Repository | mikusnuz/cws-mcp ↗ |
What it does
Lets an AI agent upload, publish, check status of, and stage rollout for a Chrome extension via the Chrome Web Store API without the CWS dashboard.
Who is it for?
Solo builders shipping Chrome extension releases
Skip if: Non-Chrome extension stores
What you get
Upload, publish, and roll out extensions from your agent.
- published extension
- staged rollout
By the numbers
- stdio transport
- npm package cws-mcp
Recommended MCP Servers
How it compares
Chrome Web Store only; not for Firefox/Edge add-on stores.
FAQ
What does the CWS MCP server do?
It uploads, publishes, checks status, and manages staged rollout for Chrome extensions via the Chrome Web Store API.
What credentials does it need?
Google OAuth2 client ID, client secret, and a refresh token for the Chrome Web Store API.