Skip to main content
Glama
ESnark

Vite MCP Server

by ESnark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Vite MCP Server

No user-submitted related servers found.

    Related Servers

    • Vue MCP

      Klipsik
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a running Laravel + Vue application to AI clients through a Vite dev-server overlay, letting them read the component tree, component state, router info, and Pinia tree/state, and also edit component state and highlight components in the browser. It auto-detects Laravel projects and registers itself in IDE config files such as Cursor, opencode, and kilo.
      MIT

    • MCP Feedback Enhanced (Hunter

      olojiang
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interactive feedback sessions in Cursor with support for multiple chat tabs, clipboard (copy/paste images), and robust connection management across multiple windows.
      13 npm
      MIT

    • VSCode MCP

      RainerKimura
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to access real-time VSCode LSP diagnostics, type information, and code navigation without slow tsc/eslint checks, plus symbol renaming and file operations.
      -

    • Cursor MCP Server

      Buga-luga
      A
      license
      Not graded
      quality
      D
      maintenance
      Facilitates integration with the Cursor code editor by enabling real-time code indexing, analysis, and bi-directional communication with Claude, supporting concurrent sessions and automatic reconnection.
      8 npm
      39
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 16 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources