Chrome Enterprise Premium MCP Server

A Model Context Protocol (MCP) server for Chrome Enterprise Premium (CEP). CEP extends Chrome’s built-in security with Data Loss Prevention (DLP), real-time threat protection (phishing and malware scanning), and Context-Aware Access controls. This server exposes CEP’s DLP rules, content detectors, connector policies, browser telemetry, and license management as MCP tools, so any MCP-compatible AI agent can inspect and configure a Chrome Enterprise environment.

Prerequisites

Before setting up the MCP server, ensure you have the following:

1. Node.js & npm: Node.js version 20.0.0 or higher installed locally.
2. Google Workspace Account:
   • Any Workspace edition with a Chrome Enterprise Premium license.
   • An administrator role in the Admin Console. Note that Super Admin is required for DLP features and running full diagnostics, while delegated roles with Chrome Management permissions are sufficient for other tools (see Administrator Role Requirements for details). Standard Workspace accounts (or Google Cloud IAM permissions alone) do not grant access.
3. OAuth App Trust (if required): If your organization restricts third-party app access, a Super Admin must trust the OAuth client in the Admin Console before you can authenticate.
4. MCP Client: A compatible MCP host application (such as Gemini CLI, Claude Desktop, Cursor, Windsurf, or VS Code).

---

Quick start

Get up and running in less than 2 minutes using the bundled Google-managed OAuth client. No repository cloning required!

1. Connect your MCP client

The server uses stdio transport; your MCP client launches it as a child process. Depending on your client, connect the server using one of the following methods:

If you are using the Gemini CLI, you can install this repository directly as an extension with a single command. This automatically configures the MCP connection and loads the built-in AI guidance rules:

gemini extensions install https://github.com/google/chrome-enterprise-premium-mcp

For all other MCP-compatible clients (such as Claude Desktop, Cursor, Windsurf, or VSCode), add this configuration block to your client’s settings file (e.g., claude_desktop_config.json or ~/.gemini/settings.json):

{
  "mcpServers": {
    "cep": {
      "command": "npx",
      "args": ["-y", "@google/chrome-enterprise-premium-mcp@latest"],
      "env": { "GCP_STDIO": "true" }
    }
  }
}