What this error means

Chrome crashes on any page-interacting MCP op (navigate / get_page_text) against a SharePoint Online tenant is a Claude Code failure pattern reported for developers trying to fix chrome crash in claude code mcp operations when interacting with sharepoint online, affecting enterprise microsoft 365 deployments. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #59988 on anthropics/claude-code, opened May 17 2026. Labels: area:chrome, area:mcp, bug, has repro. Enterprise SharePoint use case adds strong commercial value. Source: https://github.com/anthropics/claude-code/issues/59988.

Common causes

  • GitHub issue #59988 on anthropics/claude-code, opened May 17 2026. Labels: area:chrome, area:mcp, bug, has repro. Enterprise SharePoint use case adds strong commercial value. Source: https://github.com/anthropics/claude-code/issues/59988.

Quick fixes

  1. Confirm the exact error signature matches Chrome crashes on any page-interacting MCP op (navigate / get_page_text) against a SharePoint Online tenant.
  2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
  3. Check the build output, project root, and deployment platform configuration before redeploying.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.