Vite MCP Server

Name: Vite MCP Server
Author: ESnark

@ESnark

Repository Homepage

About Vite MCP Server

MCP Server for Frontend dev environment (formerly known as vite-mcp-server)

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "blowback": {
      "command": "npx",
      "args": [
        "-y",
        "blowback-context"
      ],
      "env": {
        "PROJECT_ROOT": ""
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Vite MCP Server?

Vite MCP Server (now named Blowback) integrates front-end development servers with AI tools like Claude Desktop and Cursor via the Model Context Protocol. It allows AI assistants to observe and interact with a running development server to assist with debugging and testing.

How to use Vite MCP Server?

Add the server to your MCP configuration (Claude Code: {PROJECT_ROOT}/.mcp.json; Cursor: {PROJECT_ROOT}/.cursor/mcp.json) with command npx -y blowback-context and the optional PROJECT_ROOT environment variable. Then the AI can call the available tools.

Key features of Vite MCP Server

Integration of local development server with MCP
Browser console log capture and transmission
Checkpoint-based log and snapshot management
Screenshot capture with SQLite metadata storage
HMR (Hot Module Replacement) event monitoring
Browser automation and element inspection

Use cases of Vite MCP Server

Debugging HMR events during development with AI assistance
Capturing and analyzing browser console logs automatically
Taking screenshots of the current page for visual inspection
Inspecting element properties, styles, and dimensions through AI
Monitoring network requests during a specific duration

FAQ from Vite MCP Server

What front-end development servers are supported?

The server originally only supported Vite, but now (as Blowback) aims to support various FE development servers.

Does the server require an active HMR connection?

No, HMR connection is optional. HMR monitoring starts automatically when the browser is launched.

How are screenshots stored?

Screenshots are saved as files in {PROJECT_ROOT}/.mcp_screenshot/. Their metadata is managed in a SQLite database in the temporary directory.

Is Cursor Chat supported for the `init` prompt?

No, Cursor Chat does not support MCP prompt functionality. Claude Code is recommended for that feature.

Are base64 images included in tool responses by default?

No, base64 image inclusion is controlled by the ENABLE_BASE64 environment variable, which defaults to false. Enabling it increases token usage.

Comments

More Other MCP servers

Reactive Resume

amruthpillai

A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!

39.5K