vite-mcp-server

Vite MCP Server

Blowback, formerly vite-mcp-server, connects frontend development servers with AI clients through MCP. It serves developers who need browser inspection, console logs, screenshots, and hot-reload feedback while working on local interfaces.

Server facts

vite-mcp-server

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
23
Last commit
Data as of

Overview

Frontend debugging in Blowback combines browser control with feedback from a running development server. Previously named vite-mcp-server, the project connects this workflow to AI clients such as Claude Desktop and Cursor. Its tools create, list, inspect, and close browser instances, then expose element properties, styles, dimensions, and HTML. Developers can monitor network traffic, retrieve console output, and inspect recent hot-module-replacement events. Browser interaction covers navigation, clicks, typing, selection, scrolling, and other predefined actions; a separate evaluation tool runs JavaScript within the browser context.

For visual inspection, screenshots can cover an entire page or a selected element and return resource references. Image files stay in the project’s screenshot directory, while SQLite holds their metadata for retrieval, including queries by URL path. Checkpoints associate captured state and logs with named identifiers, helping separate observations around particular changes. HMR monitoring begins when the browser launches, but an HMR connection is optional. The project uses Node.js with stdio transport, and its help tool explains individual server features.

vite-mcp-server setup notes

  • vite-mcp-server records stdio only; confirm a network transport upstream before planning remote access.
  • vite-mcp-server has no recorded license; confirm reuse terms in its repository.

Related MCP servers