Vite MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| how-to-useD | Description of how to use the server |
| start-browserB | Creates a new browser context with an auto-generated unique ID |
| list-browsersA | Lists all active browser instances |
| close-browserB | Closes a specific browser instance |
| get-context-infoC | Gets detailed information about a specific browser instance |
| get-context-statsC | Gets usage statistics for browsers |
| get-hmr-eventsC | Retrieves recent HMR events |
| capture-screenshotA | Captures a screenshot of the current page or a specific element. Stores the screenshot in the MCP resource system and returns a resource URI. If ENABLE_BASE64 environment variable is set to 'true', also includes base64 encoded image in the response. |
| get-element-propertiesB | Retrieves properties and state information of a specific element |
| get-element-stylesC | Retrieves style information of a specific element |
| get-element-dimensionsB | Retrieves dimension and position information of a specific element |
| monitor-networkA | Monitors network requests in the browser for a specified duration |
| get-element-htmlA | Retrieves the HTML content of a specific element and its children with optional depth control |
| get-console-logsB | Retrieves console logs from the development server |
| execute-browser-commandsB | Executes a sequence of predefined browser commands safely. Available commands:
Note on coordinates: For all mouse-related commands (click, drag, etc.), coordinates are relative to the browser viewport where (0,0) is the top-left corner. X increases to the right, Y increases downward. Examples are available in the schema definition. |
| browser-evaluateB | Evaluates JavaScript code directly in the browser context and returns the result. Supports expressions, function strings, and complex code with automatic execution handling. Can target the entire page or work with element handles for precise DOM manipulation. Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| init |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| screenshots |
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose: browser lifecycle (start, close, list), interaction (evaluate, screenshot, command sequence), inspection (element dimensions, HTML, properties, styles), and Vite-specific (console logs, HMR events, network monitor). No ambiguous overlap.
All tool names use a consistent hyphenated lowercase verb-noun pattern (e.g., get-element-html, list-browsers, start-browser). Naming is predictable and uniform.
16 tools is slightly above the ideal range of 3-15, but the set is well-scoped for the server's dual purpose of Vite dev server interaction and browser automation, without feeling bloated.
The tool set covers the full lifecycle (start, close, list), interactions (evaluate, screenshot, command sequences), element inspection, and Vite-specific diagnostics (console logs, HMR events, network monitoring). No obvious gaps for the intended use case.