Skip to main content
Glama

Related Servers

Alternatives to cws-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Unified 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.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Chrome extension testing. Access chrome.storage, Service Workers, declarativeNetRequest, and more directly from AI coding agents like Claude Code.
      23
      8 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A universal browser automation MCP server using Playwright, enabling programmatic control of Chrome with 63 tools for navigation, interaction, media control, and CDP-based diagnostics.
      63
      13 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local 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 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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.
      1
      Apache 2.0

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues