cws-mcp

MCPcommunity
v2.0.0mikusnuzMITUpdated 6d agonpmGitHub

MCP server for Chrome Web Store extension management

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
238Downloads/wk
4GitHub stars
1Forks
6d agoLast update
Needs 3 credentials before it runs
  • CWS_CLIENT_IDOAuth apprequired

    Google OAuth2 Client ID for Chrome Web Store API

  • CWS_CLIENT_SECRETOAuth apprequired

    Google OAuth2 Client Secret

  • CWS_REFRESH_TOKENOAuth apprequired

    OAuth2 Refresh Token

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authormikusnuz
LicenseMIT
Version2.0.0
Sourcenpm+mcp-registry
npmcws-mcp
GitHubmikusnuz/cws-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · 1 privileged
Security scan✓ Cleanv2.0.0 · todayHow well does this scan work?
EvalsNone
IndexedOct 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · 1 privileged
Statically extracted from the published packagev2.0.0 · 15h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

uploadprivilegedUpload 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.

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.

No input schema was published for this tool.

publishPublish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.

Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.

No input schema was published for this tool.

statusFetch 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.

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.

No input schema was published for this tool.

cancelCancel a pending submission on Chrome Web Store. Can be used to cancel an item currently in review.

Cancel a pending submission on Chrome Web Store. Can be used to cancel an item currently in review.

No input schema was published for this tool.

deploy-percentageSet 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.

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.

No input schema was published for this tool.

getFetch 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.

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.

No input schema was published for this tool.

get-metadata-uiRead the current draft listing description, category, homepage and support URL from the signed-in Developer Dashboard. This is not the published listing.

Read the current draft listing description, category, homepage and support URL from the signed-in Developer Dashboard. This is not the published listing.

No input schema was published for this tool.

update-metadataSave and verify draft listing fields through the Developer Dashboard.

Save and verify draft listing fields through the Developer Dashboard.

No input schema was published for this tool.

update-metadata-uiSave and verify draft listing fields through the Developer Dashboard.

Save and verify draft listing fields through the Developer Dashboard.

No input schema was published for this tool.

9 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for Chrome Web Store extension management

Keywords
mcpchrome-web-storechrome-extensionpublishmodel-context-protocol
Alternatives
Comparing tool surfaces…

Tools exposed

9 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-13 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

57 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+45 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.