cws-mcp
Related Servers
Alternatives to cws-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceUnified MCP server for browser automation (Playwright + CDP + CLI) and bookmark management across Chrome, Firefox, Edge, and Brave, including cross-browser sync, deduplication, and a React dashboard.1MIT
- AlicenseAqualityDmaintenanceMCP server for Chrome extension testing. Access chrome.storage, Service Workers, declarativeNetRequest, and more directly from AI coding agents like Claude Code.238 npm1MIT
- AlicenseBqualityDmaintenanceA universal browser automation MCP server using Playwright, enabling programmatic control of Chrome with 63 tools for navigation, interaction, media control, and CDP-based diagnostics.6313 npm3MIT
- AlicenseNot gradedqualityDmaintenanceLocal MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.221 npm3MIT
- FlicenseAqualityDmaintenanceEnterprise web automation testing MCP server that controls local Chrome via Playwright CDP, providing tools for page element analysis, interaction, dynamic layer exploration, VTable scene graph, test recording, and Shadcn-style Excel export.24-
- AlicenseNot gradedqualityBmaintenanceMCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.1Apache 2.0
TDQS
Scored across 9 tools
Two pairs of tools are near-duplicates: 'update-metadata' and 'update-metadata-ui' share identical descriptions, and 'get' is explicitly documented as an alias of 'status'. An agent has no reliable basis for choosing between the members of each pair, though the remaining tools (upload, publish, cancel, deploy-percentage) are distinguishable.
All names use kebab-case, but the verb styles vary: bare imperatives (publish, cancel, upload, get), a noun (status), a noun phrase (deploy-percentage), and compound action names (update-metadata-ui, get-metadata-ui). The '-ui' suffix convention appears meaningful but is applied inconsistently since the non-'-ui' variant has the same description.
Nine tools is a reasonable scope for a Chrome Web Store publishing workflow. The count is slightly inflated by two redundant/aliased tools that could be collapsed.
The core lifecycle (upload, publish, status, cancel, staged rollout, metadata draft) is covered, but notable gaps remain: no item creation, no published-listing metadata read (only drafts via the dashboard), no icon/package title edits, and no takedown operation. Some gaps reflect API v2 limits, but agents will hit dead ends.