Skip to main content
Glama
mikusnuz

cws-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to cws-mcp

No user-submitted related servers found.

    Related Servers

    • browser-mcp

      The-Syntax-Slayer
      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

    • crx-mcp

      youichi-uda
      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
      0
      1
      MIT

    • browser-mcp-server

      ricardodeazambuja
      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
      9 npm
      3
      MIT

    • chrome-mcp

      wzxklm
      A
      license
      Not graded
      quality
      B
      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.
      82 npm
      3
      MIT

    • kilogent-browser

      codebridger
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes, but update-metadata and update-metadata-ui both update metadata via different methods, which could cause confusion. The descriptions help differentiate, but an agent might still misselect.

    Naming Consistency4/5

    Tool names consistently use lowercase with hyphens, but there is a mix of verbs (cancel, publish, upload) and nouns (status, deploy-percentage). The hyphenation pattern is consistent.

    Tool Count5/5

    8 tools cover the core operations for Chrome Web Store item management without being overwhelming. The count is well-scoped for the server's purpose.

    Completeness3/5

    The set covers publishing workflow well, but misses important operations: creating new items (must use dashboard), listing items, and deleting. These gaps could hinder agents needing full lifecycle management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources