Telemetry enabled by default without explicit opt-in

[GaboITB]

Summary

The MCP server sends usage telemetry to Google Clearcut (play.googleapis.com/log) by default, without asking for user consent on first run.

What is sent

• MCP client name (Claude Code, Cursor, Gemini, etc.)
• Tool names invoked (click, take_screenshot, evaluate_script, etc.)
• Success/failure status
• Bucketed latency
• OS and app version
• Session UUID

No page content, URLs, or user data is sent.

Issue

While the data collected is not sensitive, telemetry should follow an opt-in model rather than opt-out, especially for a tool that has access to browser sessions (potentially authenticated pages, internal tools, etc.).

The --no-usage-statistics flag exists but is not documented prominently and is not the default.

Suggestion

• Default to --no-usage-statistics (opt-in instead of opt-out)
• Or prompt the user on first run to choose
• Or at minimum, display a clear notice at startup that telemetry is active

Found during a security audit of MCP servers.

[nroscino]

Hi!
Thank you for filing the issue. The usage statistics are intentionally on by default to improve the mcp server. As you also mentioned we are not collecting any page content or user data.
There's a dedicated section in the README.md file that highlights this. It explains the data collection and the usage of the --no-usage-statistics flag here.

Also upon the start of the MCP server, there's a console message that also brings the information to the attention of the user: