$ loading_
Forward browser console issues to AI for faster natural-language web debugging.
The material indicates this MCP tool mainly forwards browser console errors/warnings to Claude Code for debugging. It declares no required secrets or remote endpoints and is open-source under MIT; no concrete high-risk red flags are evident, but its code-execution nature and weak community validation warrant cautious use.
The material explicitly states there are no required keys or environment variables; no API key, token, or account credential requirement is described, so credential exposure appears low.
No remote endpoint host is declared. The description only mentions forwarding browser console errors to Claude Code via MCP, and based on the provided material there is no factual indication of data being sent to external third-party services.
The objective checks mark this tool as executes-code, indicating it can run code/processes in the local environment. This is a standard sensitive capability for MCP tools and warrants controlled use, but by itself is not enough to classify it as high risk.
The description indicates it accesses and forwards browser console errors, warnings, and unhandled rejections. Such debugging data may contain page context, URLs, or stack traces. The material does not show broad filesystem access, but debugging content exposure should still be minimized.
There is a public GitHub repository and the project is open-source under MIT, making the code in principle auditable, which lowers risk. However, the source is a third-party registry, community adoption is only 0 stars, and maintenance status is unknown, so trust and maturity are limited; review the source and dependencies first.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "pigeon" yet — see the docs or source repo.
I have forwarded browser console logs through pigeon. Analyze the current errors, warnings, and unhandled promise rejections, identify the most likely root cause, and provide fix steps with example code.
A root-cause analysis of the console issues, a debugging sequence, and directly applicable fix suggestions.
Based on the browser warnings forwarded by pigeon, rank them by severity and explain which ones affect functionality, performance, or compatibility; also provide a priority level for each warning.
A prioritized warning report that helps decide which issues to fix first.
Using the console errors and clues provided by pigeon, generate a step-by-step debugging checklist, including files to inspect, likely code locations, validation methods, and regression test suggestions after the fix.
A structured debugging plan that helps developers systematically locate and verify the fix.
Browse pages, inspect console/network logs, and crawl HTML documentation links.
Debug web apps through Chrome DevTools using natural language commands.
Provide AI coding tools with live UI annotations, screenshots, and structured context.
Collect visual browser feedback and send actionable annotations to Claude Code.
Automate browser testing and debug web issues directly through MCP.
Control the Comet browser via DevTools for automation, interaction, and debugging.