mozilla/firefox-devtools-mcp/diagnose
Claude Code and agent skill by mozilla/firefox-devtools-mcp
- community
Checking that the SKILL.md file is still in the repository.
Diagnose Firefox DevTools MCP setup issues. Activate when the firefox-devtools-mcp plugin fails to connect, its tools are not available, or the user reports Firefox DevTools not working in Cowork.
Install
npx vskill@latest install mozilla/firefox-devtools-mcp/diagnoseSKILL.md
When Firefox DevTools MCP tools are unavailable or the user reports issues with the firefox-devtools-mcp plugin, run this diagnostic sequence automatically. Do not ask the user to do these checks manually.
Diagnostic Steps
1. Check Node.js
Run node --version using the Bash tool.
- If the command fails with "command not found": tell the user Node.js is not installed and direct them to download Node.js 20.19.0 or higher from https://nodejs.org.
- If the version is below 20.19.0: tell the user their Node.js version is too old and they need to upgrade to 20.19.0 or higher from https://nodejs.org.
- If the version is 20.19.0 or higher: Node.js is not the issue, continue to the next check.
2. Check Your Own Tool List
Check whether any firefox-devtools-mcp:* tools are present in your current tool list.
- If present: the plugin is installed and connected in this conversation. The reported issue is not a setup problem — investigate the specific tool failure directly (bad arguments, target page state, etc.) rather than continuing this checklist.
- If absent: this is ambiguous by itself. An empty tool list looks identical whether the plugin isn't installed, the user is in the Chat tab instead of Cowork, or the plugin is installed in Cowork but failing for some other reason. Do not guess which; continue to the next step.
3. Check Installation and Tab Together
Since an absent tool list can't be attributed to a single cause from your side, ask the user to confirm both of the following in one pass:
- Open Customize > Plugins in Claude Cowork and confirm
firefox-devtools-mcpappears in the list. - Confirm they are currently in the Cowork tab, not the Chat tab — plugins only work in Cowork.
- If the plugin is missing: direct them to the installation steps at https://github.com/mozilla/firefox-devtools-mcp.
- If the plugin is present but they were in Chat: ask them to switch to Cowork and retry.
- If the plugin is present and they are already in Cowork: continue to the next step.
4. Escalate
If all checks pass and the plugin still does not work, tell the user to report the issue:
- File a bug on Bugzilla
- Or ask in the #firefox-devtools-mcp Matrix room
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/firefox-devtools-troubleshoot/skills/diagnose/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/mozilla/firefox-devtools-mcp/diagnose)