Google WebMCP

Use this skill to operate Google Search and Gemini through the built-in --site google bridge preset in @webmcp-bridge/local-mcp.

For generic bridge setup patterns or non-Google sites, switch to $webmcp-bridge.

Prerequisites

• - uxc is installed and available in PATH.
• INLINECODE5 is installed and available in PATH.
• Network access to https://www.google.com and https://gemini.google.com.
• On a fresh machine, or under an isolated HOME, install Playwright browsers first with npx playwright install.
• Gemini is auth-sensitive. Expect bootstrap_then_attach behavior when the profile is not signed in yet.

Core Workflow

1. 1. Ensure the fixed Google link exists:

1. 2. Inspect the bridge and tool schema before calling tools:

1. 3. Check authentication state first when Gemini may need sign-in:

1. 4. Use search tools for public search results:

1. 5. Use Gemini through the same authenticated browser profile:

1. 6. Use debug and navigation helpers only when necessary:

1. 7. Parse JSON output only:

Default Target

The built-in preset uses:

CODEBLOCK0

The default profile path is:

CODEBLOCK1

Refresh the link with:

CODEBLOCK2

Guardrails

• - Keep the Google profile isolated from other sites.
• Google uses bootstrap_then_attach; do not expect Gemini tools to work until the managed profile is authenticated.
• Prefer explicit bridge.session.mode.set over relaunching the command to change runtime mode.
• Long Gemini generations can legitimately take minutes. Increase timeoutMs instead of spawning parallel retries.
• INLINECODE38 works on visible generated images in the current or target conversation. Do not assume it can recover images that are no longer visible.
• INLINECODE39 must stay on Google-owned hosts only.
• If the user closes the visible Google window manually, the headed owner session ends. Run google-webmcp-cli bridge.open again if you still need a visible session on the same profile.

References

• - Common command patterns:

• - Link creation helper: