QIT

Provides an MCP server that wraps the QIT CLI for natural language testing and agent-based workflows in WordPress/WooCommerce plugin testing.
  • javascript

0

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "woocommerce-qit-mcp": {
      "command": "node",
      "args": [
        "/path/to/qit-mcp/dist/index.js"
      ],
      "env": {
        "QIT_CLI_PATH": "/path/to/qit-cli/qit"
      }
    }
  }
}

You deploy a dedicated MCP server that wraps the QIT CLI to let you drive WordPress/WooCommerce plugin testing with natural language commands and agent-based workflows. This server exposes all essential QIT CLI functionality through MCP tools and automatically detects the QIT CLI location for seamless operation.

How to use

Connect your MCP client to the server via stdio. You can issue natural language requests that map to QIT CLI actions, such as authenticating, running tests, managing environments, handling test results, and configuring packages. Use conversational commands to perform tasks like running a security test on a plugin, starting a local test environment, listing recent tests, or inspecting test reports.

How to install

Prerequisites: Node.js 18 or newer and the QIT CLI installed and accessible on your system.

Clone the MCP server repository, install dependencies, and build the project.

Additional notes

Configuration examples show how to wire the MCP server to Claude Code or other clients. The MCP server detects the QIT CLI in this order: QIT_CLI_PATH environment variable, qit in system PATH, or a local vendor path.

{
  "mcpServers": {
    "qit": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/qit-mcp/dist/index.js"],
      "env": {
        "QIT_CLI_PATH": "/path/to/qit-cli/qit"
      }
    }
  }
}

Configuration

Your MCP client can reference the QIT MCP server using the following stdio configuration. This maps the local node process to the MCP server that wraps the QIT CLI.

{
  "mcpServers": {
    "qit": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/qit-mcp/dist/index.js"],
      "env": {
        "QIT_CLI_PATH": "/path/to/qit-cli/qit"
      }
    }
  }
}

Available tools

authenticate

Connect to WooCommerce.com Partner Developer account

get_auth_status

Check current authentication status

run_test

Run any test type (security, e2e, phpstan, activation, etc.)

run_test_group

Run a predefined test group from qit.json

get_test_result

Get test result(s) by ID

list_tests

List test runs with filters

get_test_report

Get detailed test report

open_test_result

Open result in browser

get_group_status

Fetch status of a registered test group

start_environment

Start a local test environment

stop_environment

Stop a running environment

list_environments

List running environments

exec_in_environment

Execute command in environment container

reset_environment

Reset environment database

manage_package

Manage test packages (publish, download, scaffold, delete, show)

list_packages

List available test packages with filtering

manage_config

Manage backends, partners, and tunneling configuration

list_extensions

List extensions you can test

validate_zip

Validate a plugin ZIP file

manage_cache

Manipulate QIT cache

get_qit_dir

Get QIT config directory path

sync_cache

Re-sync with QIT Manager

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational