This MCP server facilitates the management of Chrome Web Store extensions, allowing users to upload, publish, and check the status of their extensions directly from Claude Code or any MCP client.
From the registry: MCP server for Chrome Web Store — extension upload, publish, status, and rollout
Please install the `cws` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Create OAuth2 credentials** — In Google Cloud Console, enable Chrome Web Store API and create Desktop-app OAuth2 credentials. (https://console.cloud.google.com/)
- **Obtain refresh token** — Exchange authorization code for a refresh token.
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","cws-mcp"]
- required environment variables:
- `CWS_CLIENT_ID`: Google OAuth2 client ID. (example: `<your-client-id>.apps.googleusercontent.com`)
- `CWS_CLIENT_SECRET`: Google OAuth2 client secret. (example: `<your-client-secret>`)
- `CWS_REFRESH_TOKEN`: OAuth2 refresh token. (example: `<your-refresh-token>`)
- `CWS_PUBLISHER_ID`: Chrome Web Store publisher ID (usually 'me'). (example: `me`)
- `CWS_ITEM_ID`: Chrome Web Store extension item ID. (example: `<your-extension-id>`)
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CWS_CLIENT_IDrequiredGoogle OAuth2 Client IDCWS_CLIENT_SECRETrequiredGoogle OAuth2 Client SecretCWS_REFRESH_TOKENrequiredOAuth2 Refresh TokenReal-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.