MCP Tools DirectoryAbout this integration
MCP server for Chrome Web Store — extension upload, publish, status, and rollout
- Transport
- stdio
- Authentication
- oauth
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.4.1
- Package
- cws-mcp
- Last compatibility test
- Not independently tested
Connect your agent
cws-mcpThe documented API tools use a client ID, client secret, and refresh token obtained through one-time Google OAuth authorization. The unattended scope does not include update-metadata-ui: the publisher says its first browser-automation run may require an interactive login and persistent profile. The package was not executed or independently security-audited.
Capabilities: Upload Chrome extension packages, Publish, cancel, and stage Chrome extension rollouts, Read Chrome Web Store review and deployment status, Read and update listing metadata through documented API tools
Connected profiles
Additional details
io.github.mikusnuz/cws
Source ↗ · Checked 2026-09-171.4.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN
Source ↗ · Checked 2026-09-17cws-mcp
Source ↗ · Checked 2026-09-191.4.3
Source ↗ · Checked 2026-09-19Token-backed API tools can run from the configured local stdio process after one-time OAuth authorization; dashboard UI automation is excluded because its first run may require login.
Source ↗ · Checked 2026-09-19Google OAuth2 client ID, client secret, and refresh token are required; obtaining the refresh token requires an initial user authorization step.
Source ↗ · Checked 2026-09-19MCP clients run npx -y cws-mcp over stdio with Chrome Web Store OAuth values supplied as environment variables.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19