Skip to main content
Glama
kitepon

Chrome Ops MCP

by kitepon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Chrome Ops MCP

No user-submitted related servers found.

    Related Servers

    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

    B3.1/5.0

    Scored across 24 tools

    Disambiguation4/5

    Tools are mostly distinct, with clear separation between status, tabs, DevTools capture, extension management, and content settings. The network family has some overlap, but each tool is scoped specifically enough to avoid serious misselection.

    Naming Consistency4/5

    Most tools follow a resource_verb snake_case pattern such as tabs_list, extension_get, and content_setting_set. Minor inconsistencies like chrome_status and extension_dev_errors, plus singular/plural variations, keep this from being a perfect 5.

    Tool Count3/5

    At 24 tools, the server is at the heavy end and includes very granular network and extension-dev groupings. The broad Chrome Ops scope justifies many tools, but the count feels borderline compared to a tighter, well-scoped server.

    Completeness3/5

    The surface covers connection health, tab activation, DevTools monitoring, runtime evaluation, extensions, and content settings. Obvious gaps like tab creation/closing and direct URL navigation are missing, though agents can partially work around them with runtime_evaluate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources