Skip to main content
Glama
djankies

Vitest MCP Server

by djankies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Vitest MCP Server

No user-submitted related servers found.

    Related Servers

    • testmcp

      r-marques
      F
      license
      A
      quality
      D
      maintenance
      Wraps existing test frameworks (Jest, Vitest, Pytest) and exposes structured, LLM-optimized results via MCP tools with progressive disclosure and diff-aware execution.
      11
      1
      -

    • Test Analyzer MCP Server

      giri-jeedigunta
      F
      license
      C
      quality
      D
      maintenance
      Enables comprehensive analysis of JavaScript/TypeScript project testing setups by detecting frameworks like Jest, Vitest, and Cypress, analyzing test coverage metrics, and generating actionable recommendations for improving test quality. Provides detailed insights into test structure, dependencies, and coverage thresholds with visual feedback.
      3
      1
      -

    • tuxedo-qa

      jonathan-ponciano
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to create, run, autocorrect, and monitor Playwright tests for your app with a local dashboard, credential vault, and public status page.
      16
      MIT

    • vitest-migrator-mcp

      Manvi1203
      F
      license
      A
      quality
      B
      maintenance
      Enables automated migration of JavaScript/TypeScript packages from legacy test runners like Karma, Webpack, and Mocha to Vitest, including AST codemods, multi-project test scaffolding, and self-learning diagnostics for resolving runtime errors.
      7
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: listing tests, running tests, analyzing coverage, and setting root. No overlap or ambiguity.

    Naming Consistency4/5

    Tools follow a consistent verb_noun pattern: list_tests, run_tests, analyze_coverage, set_project_root. Minor deviation with set_project_root (not a test-specific verb), but still clear.

    Tool Count5/5

    With 4 tools, the server is well-scoped for test discovery, execution, coverage analysis, and configuration. Each tool is essential and no redundancy.

    Completeness4/5

    The tool set covers the core testing lifecycle: discovering tests, running them, analyzing coverage, and setting up the project root. Minor gap: no tool for watching tests or filtering specific test names, but agents can work around via run_tests.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources