troubleshooting-webmobai-setup

Diagnoses WebMobAI installation, MCP wiring, and browser session failures using webmobai-doctor.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/celikgo/webmobai --skill troubleshooting-webmobai-setup-celikgo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshooting-webmobai-setup
Source: https://github.com/celikgo/webmobai/tree/main/.claude/skills/troubleshooting-webmobai-setup
Command: npx skills add https://github.com/celikgo/webmobai --skill troubleshooting-webmobai-setup-celikgo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When WebMobAI itself breaks — MCP tools missing from Claude, browsers failing to launch, Playwright engines not installed, or the desktop app flagged as damaged — this Skill provides a decision-tree workflow to isolate whether the fault is in the environment, the MCP wiring, or the live browser session. ## Core Features & Use Cases - Doctor-driven diagnosis: Runs webmobai-doctor first and branches on its six/seven checks covering Node version, Playwright engines, Lighthouse, AI API key, and storageState validity. - Layered fault isolation: Distinguishes environment failures (Node < 18, missing Chromium), wiring failures (MCP server not appearing in Claude Desktop or Claude Code), and session-state failures (browser not launched, already running, idle-timeout auto-close). - Use Case: A user says "none of the webmobai tools show up in Claude Code." The Skill walks the .mcp.json config, validates JSON and command paths, confirms dist/index.js is built, and has the user run npx -y webmobai-mcp by hand to read the real stderr error. ## Quick Start Run webmobai-doctor and use the troubleshooting skill to diagnose why my WebMobAI tools are not working.

Frequently Asked Questions about troubleshooting-webmobai-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix WebMobAI tools not showing up in Claude?▼

Missing webmobai_* tools indicate MCP wiring failure, not environment. Validate the claude_desktop_config.json or .mcp.json file for JSON errors, use an absolute command path if npx is not on the host PATH, ensure dist/index.js is built for source checkouts, then restart the host.

How to fix "Browser is not launched" error in WebMobAI?▼

Call webmobai_launch_browser first, since most tools require an active browser session. If you already launched, check whether idle_timeout_ms auto-closed the browser after inactivity, then call webmobai_close_browser and relaunch.

Does WebMobAI work without an Anthropic API key?▼

Yes, all tools work without a key except webmobai_summarize_audit, webmobai_explain_visual_diff, and webmobai_generate_scenario_from_prompt. Those three return an "AI features are disabled" message as normal text. Set WEBMOBAI_ANTHROPIC_API_KEY in the MCP host env block to enable them.

Why does macOS say the WebMobAI app is damaged?▼

Current WebMobAI desktop releases are not signed or notarized, so Gatekeeper quarantines the .dmg. Strip the quarantine attribute once with xattr -cr /Applications/WebMobAI.app. This affects only the desktop app, never the npm package or CLI binaries.

Why does webmobai-doctor pass but the browser still fails to launch?▼

Doctor only verifies the Chromium executable exists on disk; it never launches a browser. Sandbox restrictions, missing shared libraries, or corrupt downloads still fail at launch. Read the Playwright error verbatim for the real diagnostic.

When should I not use this troubleshooting skill?▼

Do not use it for failing tests on a working setup. A selector that stopped matching belongs to selector debugging, and a genuinely broken page belongs to smoke-test workflows. This skill only fixes WebMobAI itself, not the site under test.