From a87302b89d15978757833be9da1d5d895e10cfc4 Mon Sep 17 00:00:00 2001 From: Daniel Kastl Date: Tue, 10 Feb 2026 10:55:00 +0900 Subject: [PATCH] docs: add macOS Bluetooth permission troubleshooting note --- docs/troubleshooting.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 6a7e36bc9..1be6efbd5 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -55,6 +55,16 @@ This indicates that the browser could not be started. Make sure that no Chrome instances are running or close them. Make sure you have the latest stable Chrome installed and that [your system is able to run Chrome](https://support.google.com/chrome/a/answer/7100626?hl=en). +### Chrome crashes on macOS when opening Web Bluetooth + +On macOS, Chrome launched by an MCP host app may crash with a macOS privacy +permission violation (TCC, "Transparency, Consent, and Control") when a native +Bluetooth chooser opens. + +Grant Bluetooth permission to the MCP host app in +`System Settings > Privacy & Security > Bluetooth`, then restart the MCP host +app and Chrome MCP session. + ### Remote debugging between virtual machine (VM) and host fails When connecting DevTools inside a VM to Chrome running on the host, any domain is rejected by Chrome because of host header validation. Tunneling the port over SSH bypasses this restriction. In the VM, run: