How to Set Up GitHub Copilot in VS Code With testRigor CLI, MCP, and Skills on Windows

Kevin Carroll

You can connect GitHub Copilot in Visual Studio Code to testRigor so that Copilot can help you create, run, troubleshoot, and maintain automated tests.

You do not need programming experience or previous command-line experience to complete this setup.

This guide walks through setting up the testRigor CLI, MCP server, and testRigor Skills with GitHub Copilot built into Visual Studio Code on Windows.

How it Works:

GitHub Copilot + testRigor

There are four important pieces in this setup. They work together, but each has a different job.

🤖

GitHub Copilot

Your AI coding agent

Copilot works inside VS Code and lets you describe what you want to accomplish in normal language.

⌨️

testRigor CLI

Command-line access

Allows testRigor operations to be performed from the command line instead of only through the web interface.

🔗

MCP

Connect Copilot to testRigor

Allows Copilot in VS Code to communicate directly with testRigor and use the tools provided by the testRigor MCP server.

🧠

testRigor Skills

Teach Copilot testRigor

Give Copilot testRigor-specific instructions for writing tests, using the CLI, and following testRigor workflows.

The complete setup: Prepare VS Code → Install the testRigor CLI → Add the testRigor Skills → Connect testRigor through MCP → Enable the MCP tools → Start working.

Prepare:

Get VS Code and GitHub Copilot Ready

Step 1 · Open Visual Studio Code

Open Visual Studio Code.

Make sure GitHub Copilot is available in VS Code.

Look for the GitHub Copilot icon in the VS Code interface.

If Copilot asks you to sign in or authorize access, follow the prompts and sign in with the GitHub account associated with your Copilot access.

Screenshot needed

VS Code showing the GitHub Copilot icon and Copilot Chat panel.

After signing in, open the Copilot Chat panel.

Depending on your GitHub account, you may be using Copilot Free or another Copilot plan. The setup in this guide does not depend on the plan name displayed in the video.

✓ Checkpoint — Continue when GitHub Copilot Chat is available inside VS Code.

Step 2 · Open PowerShell

We will use PowerShell to install the testRigor command-line tool.

Click the Windows Start button and search for:

PowerShell

Open PowerShell.

You should see something similar to:

PS C:\Users\YourName>

Your actual Windows username will appear instead of YourName.

✓ Checkpoint — Continue when PowerShell is open and you see a line beginning with PS.

Step 3 · Check Node.js

The testRigor CLI requires Node.js version 18 or newer.

Check whether Node.js is already installed:

node --version

Then check npm:

npm --version

If both commands return version numbers, continue.

If Node.js is not installed, download the current LTS version for Windows from the official Node.js website.

✓ Checkpoint — Continue when both node --version and npm --version return version numbers.

Install:

Add the testRigor CLI

Step 4 · Install the testRigor CLI

In PowerShell, run:

npm install -g @testrigor/testrigor-cli

npm will download and install the testRigor CLI and its required packages.

When the normal PowerShell prompt returns, verify the installation:

testrigor --version

You should see a testRigor CLI version number.

✓ Checkpoint — Continue when testrigor --version returns a version number.

npm says that running scripts is disabledTroubleshooting help

Try:

npm.cmd --version

If that returns a version number, use:

npm.cmd install -g @testrigor/testrigor-cli

instead of the normal npm command.

Connect:

Create Your testRigor Authentication Token

Step 5 · Generate a testRigor Personal Authentication Token

The CLI and MCP connection need permission to communicate with your testRigor account.

testRigor provides this through a Personal Authentication Token, or PAT.

In testRigor:

Click your username in the upper-right corner.
Select API Tokens.
Click Generate New Token.
Give the token a clear name, such as VS Code MCP.
Choose an expiration that follows your organization’s security policy.
Generate the token.
Copy it.

Screenshot needed

testRigor API Tokens page showing Generate New Token.

Keep this token available. You will use it to authenticate the testRigor CLI and configure the MCP server.

Treat the PAT like a password. Do not expose it in screenshots, public documentation, chat messages, or source-control repositories.

Step 6 · Authenticate the testRigor CLI

Return to PowerShell and run:

testrigor authenticate

The CLI will ask for your testRigor Personal Authentication Token.

Paste the token and press Enter.

The CLI should confirm that authentication has been saved.

✓ Checkpoint — Continue when the CLI confirms that authentication was saved.

Add the Skills:

Teach GitHub Copilot How to Work with testRigor

Step 7 · Download the testRigor Skills

testRigor Skills are reusable instruction packages that give Copilot additional guidance about how to work with testRigor.

🔁

testrigor-dev-loop

The end-to-end workflow

Helps Copilot build, run, inspect, fix, and run tests again as part of an iterative development loop.

✍️

testrigor-write-tests

Writing testRigor tests

Helps Copilot write and edit testRigor tests, reusable rules, and other testRigor test content.

⌨️

testrigor-cli

Using the CLI

Helps Copilot understand and use testRigor command-line functionality correctly.

Open the testRigor Skills repository on GitHub.

Click the Code dropdown and select Download ZIP.

Screenshot needed

GitHub testRigor Skills repository with the Download ZIP option visible.

After the ZIP file downloads, open your Downloads folder.

Step 8 · Create Copilot’s Personal Skills Folder

GitHub Copilot can discover personal Skills stored in your Windows user profile.

Navigate to:

C:\Users\YourName\.copilot

Replace YourName with your actual Windows username.

Inside the .copilot folder, create a new folder named:

skills

Your final path should look similar to:

C:\Users\YourName\.copilot\skills

Screenshot needed

Windows File Explorer showing the .copilot\skills directory.

Step 9 · Copy the testRigor Skills

Extract the downloaded testRigor Skills ZIP file.

Inside the extracted repository, locate the three testRigor Skill folders:

testrigor-cli
testrigor-dev-loop
testrigor-write-tests

Copy those three folders directly into:

C:\Users\YourName\.copilot\skills

Each Skill must remain in its own folder.

The resulting structure should look similar to:

.copilot
└── skills
    ├── testrigor-cli
    ├── testrigor-dev-loop
    └── testrigor-write-tests

✓ Checkpoint — Continue when the three testRigor Skill folders are directly inside .copilot\skills.

Step 10 · Confirm the Skills in VS Code

Return to VS Code.

Open the Copilot customization settings using the gear icon and select Skills.

You should see the three testRigor Skills:

testrigor-cli
testrigor-dev-loop
testrigor-write-tests

Screenshot needed

VS Code Skills view showing the three installed testRigor Skills.

✓ Checkpoint — Continue when the three testRigor Skills are visible in VS Code.

Add MCP:

Connect GitHub Copilot Directly to testRigor

Step 11 · Open the Project in VS Code

The video configures testRigor MCP at the workspace level. This means the MCP configuration belongs to the particular project folder you open in VS Code.

Open the folder where you want to use testRigor with GitHub Copilot.

For example, the video uses a project folder containing testRigor UI scripts.

Step 12 · Create the VS Code MCP Configuration

In the root of your project, create a folder named exactly:

.vscode

Include the period at the beginning.

Inside the .vscode folder, create a new file named:

mcp.json

Your project structure should now look similar to:

your-project
└── .vscode
    └── mcp.json

Screenshot needed

VS Code Explorer showing .vscode/mcp.json inside the project.

Step 13 · Add the testRigor MCP Server

Open .vscode/mcp.json and paste:

{
  "servers": {
    "testrigor": {
      "type": "http",
      "url": "https://api2.testrigor.com/api/v1/mcp",
      "headers": {
        "personal-access-token": "YOUR_TESTRIGOR_PAT"
      }
    }
  }
}

Replace:

YOUR_TESTRIGOR_PAT

with the Personal Authentication Token you generated earlier.

Do not leave the placeholder text in the configuration.

Save the file. On Windows, you can press:

Ctrl + S

Screenshot needed

VS Code showing the completed mcp.json configuration. Blur or replace the real PAT before publishing the screenshot.

✓ Checkpoint — Continue when the file has been saved successfully.

Step 14 · Confirm testRigor Appears in MCP Servers

Open the Copilot customization settings using the gear icon and go to MCP Servers.

You should now see testRigor listed.

Screenshot needed

VS Code MCP Servers view showing testRigor.

At this point, the server has been configured. Next, make sure its tools are enabled for Copilot Agent mode.

Step 15 · Enable the testRigor MCP Tools

Open Copilot Chat and make sure you are using Agent mode.

Open the chat’s More Actions menu and select the option to configure tools.

Find testRigor in the available tools.

Make sure the checkbox for the testRigor MCP server is enabled.

You can expand it to see the individual tools provided by the server.

Screenshot needed

Copilot Agent mode tool configuration showing testRigor MCP enabled.

✓ Checkpoint — Continue when testRigor is enabled in the Agent tools list.

Step 16 · Test the MCP Connection

Now give Copilot a simple read-only request.

For example:

Which MCP servers do you have access to?

Copilot should recognize the testRigor MCP server.

You can also try a testRigor-specific request:

List the testRigor test suites I have access to.

Copilot should use the testRigor MCP tools to retrieve the suites available to your testRigor user.

If you return to MCP Servers, VS Code may display testRigor as running after the MCP connection has been used.

Screenshot needed

VS Code showing testRigor MCP with a running or connected status indicator.

✓ Checkpoint — If Copilot can access testRigor through MCP, the connection is working.

Start Working:

Use GitHub Copilot with testRigor

At this point, GitHub Copilot has the three pieces it needs for the complete testRigor integration:

✓ testRigor CLI

Installed and authenticated with your testRigor account.

✓ testRigor MCP

Copilot can communicate directly with testRigor using MCP tools.

✓ testRigor Skills

Copilot has testRigor-specific guidance available when relevant.

You can now use Copilot Agent mode and describe what you want to do in normal English.

For example:

Help me write a testRigor test that logs in and verifies that the dashboard appears.

Or:

Run my testRigor tests and help me troubleshoot the failures.

Or:

List my test suites and show me the test cases in the suite named Regression.

Troubleshooting:

If Something Doesn’t Look Right

If everything is working, you do not need to read the sections below. Open only the problem that matches what you are seeing.

The testRigor Skills do not appear in VS CodeTroubleshooting help

Check that the three Skill folders are located directly inside:

C:\Users\YourName\.copilot\skills

You should have:

.copilot
└── skills
    ├── testrigor-cli
    ├── testrigor-dev-loop
    └── testrigor-write-tests

Do not leave them nested inside an additional downloaded repository folder such as skills-main.

If necessary, restart VS Code after moving the folders.

testRigor does not appear under MCP ServersTroubleshooting help

Make sure the file is located at:

your-project\.vscode\mcp.json

Check that the VS Code configuration uses:

"servers"

as the top-level property.

Also verify that the server contains:

"type": "http"

and that the URL is https://api2.testrigor.com/api/v1/mcp.

testRigor appears but Copilot does not use its toolsTroubleshooting help

First, make sure Copilot Chat is in Agent mode.

Then open the tools configuration from the chat’s More Actions menu.

Find testRigor and confirm that it is enabled.

MCP tools must be available to Agent mode before Copilot can invoke them.

MCP authentication failsTroubleshooting help

Check whether:

The PAT was copied completely.
The PAT has expired or been revoked.
The header is named personal-access-token.
The testRigor user associated with the token still has access.
A company firewall or network policy could be blocking the MCP connection.

MCP does not bypass testRigor permissions.

Copilot can connect but cannot access my test suiteTroubleshooting help

Try to open the same test suite there.

If that user cannot access the suite in testRigor, Copilot will not gain additional access through MCP.

Next Steps:

Go Further with GitHub Copilot and testRigor

Once the initial setup is working, you can use Copilot together with the testRigor CLI, Skills, and MCP tools for more advanced test creation, execution, troubleshooting, and maintenance workflows.

For more information, see:

Your instructions to GitHub Copilot can still be written in normal, plain English.

How to Set Up GitHub Copilot in VS Code With testRigor CLI, MCP, and Skills on Windows

How it Works:

GitHub Copilot + testRigor

Prepare:

Get VS Code and GitHub Copilot Ready

Step 1 · Open Visual Studio Code

Step 2 · Open PowerShell

Step 3 · Check Node.js

Install:

Add the testRigor CLI

Step 4 · Install the testRigor CLI

Connect:

Create Your testRigor Authentication Token

Step 5 · Generate a testRigor Personal Authentication Token

Step 6 · Authenticate the testRigor CLI

Add the Skills:

Teach GitHub Copilot How to Work with testRigor

Step 7 · Download the testRigor Skills

Step 8 · Create Copilot’s Personal Skills Folder

Step 9 · Copy the testRigor Skills

Step 10 · Confirm the Skills in VS Code

Add MCP:

Connect GitHub Copilot Directly to testRigor

Step 11 · Open the Project in VS Code

Step 12 · Create the VS Code MCP Configuration

Step 13 · Add the testRigor MCP Server

Step 14 · Confirm testRigor Appears in MCP Servers

Step 15 · Enable the testRigor MCP Tools

Step 16 · Test the MCP Connection

Start Working:

Use GitHub Copilot with testRigor

Troubleshooting:

If Something Doesn’t Look Right

Next Steps:

Go Further with GitHub Copilot and testRigor

How to Set Up Cursor With testRigor MCP, CLI, and Skills on Windows

How to Allowlist testRigor IP Addresses in Google reCAPTCHA

Best Practices on How and When to Use AI in testRigor

How it Works: GitHub Copilot + testRigor

Prepare: Get VS Code and GitHub Copilot Ready

Step 1 · Open Visual Studio Code

Step 2 · Open PowerShell

Step 3 · Check Node.js

Install: Add the testRigor CLI

Step 4 · Install the testRigor CLI

Connect: Create Your testRigor Authentication Token

Step 5 · Generate a testRigor Personal Authentication Token

Step 6 · Authenticate the testRigor CLI

Add the Skills: Teach GitHub Copilot How to Work with testRigor

Step 7 · Download the testRigor Skills

Step 8 · Create Copilot’s Personal Skills Folder

Step 9 · Copy the testRigor Skills

Step 10 · Confirm the Skills in VS Code

Add MCP: Connect GitHub Copilot Directly to testRigor

Step 11 · Open the Project in VS Code

Step 12 · Create the VS Code MCP Configuration

Step 13 · Add the testRigor MCP Server

Step 14 · Confirm testRigor Appears in MCP Servers

Step 15 · Enable the testRigor MCP Tools

Step 16 · Test the MCP Connection

Start Working: Use GitHub Copilot with testRigor

Troubleshooting: If Something Doesn’t Look Right

Next Steps: Go Further with GitHub Copilot and testRigor

How it Works:

GitHub Copilot + testRigor

Prepare:

Get VS Code and GitHub Copilot Ready

Install:

Add the testRigor CLI

Connect:

Create Your testRigor Authentication Token

Add the Skills:

Teach GitHub Copilot How to Work with testRigor

Add MCP:

Connect GitHub Copilot Directly to testRigor

Start Working:

Use GitHub Copilot with testRigor

Troubleshooting:

If Something Doesn’t Look Right

Next Steps:

Go Further with GitHub Copilot and testRigor