Google Webmcp
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is coherently focused on Google Search/Gemini browser automation, but users should notice that it relies on an authenticated Google browser profile and an external bridge helper.
This skill appears coherent for Google Search and Gemini use through a local browser bridge. Before installing, be comfortable signing into a managed Google profile under ~/.uxc/webmcp-profile/google, verify the separate webmcp-bridge/local-mcp components, and avoid using the profile for unrelated sites or sensitive accounts.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If you sign in, the skill can use that managed Google session for Gemini and related Google interactions.
The skill explicitly relies on a signed-in Google browser profile, meaning actions occur in the user's authenticated Google context.
Use Gemini through the same authenticated browser profile... The default profile path is: ~/.uxc/webmcp-profile/google
Use a dedicated Google profile/account where possible, keep the profile isolated as instructed, and review authentication state before running Gemini tools.
Installation or link refresh depends on the separate WebMCP bridge skill being present and trustworthy.
The included helper delegates link creation to another skill's webmcp-bridge script, which is not part of this artifact set. The delegation is purpose-aligned and pins the site to google, but it depends on external local bridge code.
exec "${ROOT_DIR}/skills/webmcp-bridge/scripts/ensure-links.sh" --name google --site googleVerify the referenced webmcp-bridge skill and local-mcp package before running the link helper, especially in sensitive environments.
Running setup may download and install browser components on the local machine.
The setup instructions ask the user to run an npx command to install browser components. This is expected for Playwright-based browser automation, but it is still local command execution and network installation.
On a fresh machine, or under an isolated HOME, install Playwright browsers first with `npx playwright install`.
Run setup commands only from a trusted environment and confirm they match the documented browser-automation purpose.