Skip to main content
Glama
google

Chrome Enterprise Premium MCP Server

Official
by google
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Chrome Enterprise Premium MCP Server

No user-submitted related servers found.

    Related Servers

    • Chrome Profile MCP Server

      nghiahsgs
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to control a real Google Chrome instance using specific user profiles, cookies, and extensions. It provides 18 tools for browser navigation, element interaction, and page inspection via the Chrome DevTools Protocol.
      -

    • BrowserGenie MCP Server

      BrowserGenie
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that provides AI models with full browser automation capabilities through Chrome. It enables navigation, interaction, screenshots, and complete DevTools access by bridging AI clients with a companion Chrome extension.
      99
      12 npm
      3
      Apache 2.0

    • Chrome Bookmark MCP Server

      mamba-mental
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server implementation that provides seamless integration between Chrome bookmarks and AI assistants. This server enables AI models to access, search, analyze, and manage Chrome bookmarks through a standardized protocol.
      2
      MIT

    • GCP MCP

      eniayomi
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Google Cloud Platform environments through natural language, allowing users to query and manage GCP resources during conversations.
      9
      1,504 npm
      200
      MIT
    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 25 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes (auth, DLP rules, detectors, browser management). However, there is slight overlap between some diagnostic tools (diagnose_environment, security_insights) and multiple DLP-related tools (create_chrome_dlp_rule, create_default_dlp_rules, list_dlp_rules, get_dlp_rule) could confuse an agent, though descriptions help differentiate.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., check_cep_subscription, create_chrome_dlp_rule, list_dlp_rules). Even auth tools use cep_auth as a prefix. No mixing of camelCase or other conventions, making it predictable for an agent.

    Tool Count4/5

    With 25 tools, the server is slightly above the ideal range (3-15). While all tools serve a purpose in Chrome Enterprise Premium management, the count feels a bit heavy, especially with many DLP and detector tools. Still, it remains manageable and not overly bloated.

    Completeness3/5

    The tool surface covers core operations like listing, creating, and checking licenses, but there are notable gaps: no tools to update or delete DLP rules, and no OU management beyond listing. Agents will hit dead ends when trying to modify or remove existing configurations.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources