Skip to content
Back to skills

Fix Chrome Connection

ASecurity

Diagnose and fix Chrome MCP connection issues — run after switching macOS users when Chrome won't connect

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 7, 2026
ai-agentsgobash

Works with

  • claude desktop
  • cli
  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 7, 2026

npx -y skills add MSApps-Mobile/claude-plugins --skill fix-chrome-connection --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fix Chrome Connection?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fix Chrome Connection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/msapps-mobile-fix-chrome-connection/badge)](https://www.skillsdirectory.com/skills/msapps-mobile-fix-chrome-connection)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: fix-chrome-connection
description: Diagnose and fix Chrome MCP connection issues — run after switching macOS users when Chrome won't connect
---

This is an automated run of a scheduled task. The user is not present to answer questions.
Make reasonable choices autonomously and note them in your output.
For "write" actions, only take them if explicitly required by the task.
When in doubt, produce a report of what you found.

You are fixing a broken Chrome MCP connection. Work through these steps in order,
stopping as soon as the connection works.

## Step 1: Test current connection

Call tabs_context_mcp with createIfEmpty: false.
- If it responds (any response other than a connection error) → report "Chrome is already connected!" and stop.
- If it fails with a connection error → note it and continue.

## Step 2: Screenshot the current desktop state

```bash
screencapture -x /tmp/chrome_check.png
sips -Z 1920 /tmp/chrome_check.png --out /tmp/chrome_check_small.png
```

Copy to workspace and Read it. Note what's visible (Chrome open? which app is in focus? any errors?).

## Step 3: Open Chrome

```bash
open -a "Google Chrome"
sleep 3
```

Retry connection test. If connected → report success and stop.

## Step 4: Quit and relaunch Chrome ← MOST RELIABLE FIX

Do NOT attempt to click UI elements on chrome://extensions — the Claude desktop app steals
focus from Chrome, making coordinate-based clicking fail. Go straight to quit+relaunch:

```bash
osascript -e 'tell application "Google Chrome" to quit'
sleep 5
open -a "Google Chrome"
sleep 8
```

Retry connection test. If connected → report success and stop.

## Step 5: Report failure and ask the user

If all automated steps failed, report:
- Every step attempted and what happened
- Current state of Chrome (from last screenshot)
- Ask: "Are you logged into the correct Chrome profile? After switching macOS users, Chrome
  may open under a different profile where the extension isn't installed."

## Step 6: Last resort

If the profile check doesn't help, suggest reinstalling the Claude in Chrome extension:
open chrome://extensions → remove Claude in Chrome → reinstall from Chrome Web Store.

## After each step

Report what you tried and what happened. Do not silently retry.

Files in this skill

  • CLAUDE.md5.2 KB
  • SKILL.md2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.