MCP.so
ログイン

Unit Test Generator

@hanqizheng

Unit Test Generator について

概要はまだありません

基本情報

カテゴリ

開発者ツール

ランタイム

node

トランスポート

stdio

公開者

hanqizheng

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "unit-test-generator": {
      "command": "node",
      "args": [
        "YOUR_MCP_SERVER_BUILD_INDEX_PATH"
      ],
      "env": {
        "PROJECT_PATH": "YOUR_COMPONENT_LIBRARY_PROJECT_PATH"
      },
      "transport": "stdio",
      "enabled": true,
      "description": "component library unit test generator"
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Unit Test Generator?

Unit Test Generator is an MCP server that uses the Model Context Protocol to automatically generate unit tests for component libraries. It is designed for developers working with component-based projects and integrates with Cursor via a local MCP server configuration.

How to use Unit Test Generator?

Clone the repository, install dependencies with npm install, and build with npm run build. Then add it as a global MCP server in Cursor by providing a JSON configuration that specifies the command (node), the path to the built index file, the PROJECT_PATH environment variable pointing to your component library, and the transport type (stdio).

Key features of Unit Test Generator

  • Generates unit tests for component libraries
  • Integrates with Cursor via MCP protocol
  • Uses stdio transport for local execution
  • Requires only Node.js and npm

Use cases of Unit Test Generator

  • Automatically create unit tests for a React component library
  • Maintain test coverage for a growing UI component set
  • Speed up test writing in a Cursor development workflow

FAQ from Unit Test Generator

What are the dependencies or runtime requirements?

You need Node.js and npm installed. The server is built with npm and run with the node command.

How is the server configured for Cursor?

You add it as a global MCP server in Cursor Settings, providing a JSON block that includes the command, args build index path), environment variable PROJECT_PATH, transport stdio, and enabled flag.

Where does the user data (project files) reside?

The server accesses the component library specified in the PROJECT_PATH environment variable. No external data is transferred; the server runs locally.

What transport does the server use?

It uses the stdio transport, meaning it communicates over standard input/output with the Cursor client.

Does the server require authentication?

No authentication is mentioned. The server is intended for local use only.

コメント

「開発者ツール」の他のコンテンツ