$ loading_
Provides MCP access to browsers for debugging console, storage, performance, and component trees.
The materials indicate an open-source MIT Vite/MCP-related plugin with no required secrets and no declared remote endpoints, with no clear high-risk red flags. Caution is still warranted because it has code-execution characteristics and can interact with browser-side console, cookies, storage, and related adapters, so it is best used in a controlled development environment.
The materials explicitly state that no keys or environment variables are required, and there is no indication that API tokens, account passwords, or cloud credentials are needed, so credential exposure appears low.
No remote host endpoints are declared, and the description does not show data being sent to third-party services; based on the available materials, there is no explicit outbound data path.
The system flags it as executes-code, and as a Vite/MCP plugin it would typically run within local development workflows and interact with browser environments. This is a normal capability for this class of tool, and the materials do not show requests for system privileges beyond its stated purpose.
The description says it can use adapters for console, cookies, storage, performance, and component tree inspection, which implies access to debugging and state data in the browser context. The materials do not state that it writes or exports this data, and no clear overprivilege is shown, but it should still be treated as having visibility into local development data.
Positive factors are that it is open source under the MIT license and can be audited in source form; however, it comes from a third-party registry, has 0 stars, and has unknown maintenance status, so its trust maturity is limited and supply-chain caution is appropriate.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "vite-mcp" yet — see the docs or source repo.
Connect to the current browser page, inspect console logs, summarize the error cause, and give the highest-priority fix suggestions.
A console error summary, likely causes, and fix steps.
Analyze the current page's performance, focusing on key metrics and the most obvious bottlenecks.
An overview of performance metrics and bottleneck analysis.
Inspect the current page's component tree, identify suspicious render hierarchy or abnormal component state, and provide troubleshooting suggestions.
Component hierarchy notes, anomalies, and troubleshooting suggestions.
Automate browser tasks, capture console logs, and take screenshots for web workflows.
Control a browser with AI for automation, extraction, interception, and screenshots.
Connect Chrome DevTools so AI can debug pages and inspect performance.
Control and debug running Node.js processes through a CDP-to-DAP bridge.
Extract, analyze, and clone front-end code with browser automation.
Enable multiple AI agents to automate a real Chrome browser privately.