Turn your manual testers into automation experts!Request a Demo

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

Kevin Carroll
Weekly Newsletter
Receive weekly testRigor newsletters packed with insights on test automation, codeless testing, and the latest advancements in AI.

You can connect Cursor to testRigor so that Cursor 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 is written specifically for Windows users and walks through installing the testRigor command-line tool, connecting Cursor to the testRigor MCP server, and installing the testRigor Skills. At every important step, we will tell you what to do, what you should expect to see, and how to confirm that it worked before continuing.

How it Works:
Cursor + testRigor

There are four important pieces in this setup. They work together, but each has a different job.
🤖
Cursor
Your AI coding agent
You interact with Cursor and 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 Cursor to testRigor
Allows Cursor to communicate directly with testRigor and use the tools provided by the testRigor MCP server.
🧠
testRigor Skills
Teach Cursor testRigor
Give Cursor testRigor-specific instructions for writing tests, using the CLI, and working through test failures.
The complete setup: Prepare Windows → Install the testRigor CLI → Connect Cursor through MCP → Add the testRigor Skills → Start working.

Prepare:
Get Your Windows Computer Ready

Step 1 · Open PowerShell

PowerShell is a Windows application that lets you give your computer written instructions instead of clicking buttons.
During this setup, you will mostly:
  1. Copy a command from this page.
  2. Paste it into PowerShell.
  3. Press Enter.
  4. Check the result.
You do not need to know how to write PowerShell commands yourself.
Click the Windows Start button and search for:
PowerShell
Open the normal PowerShell or Windows PowerShell application.
Do not select a version labeled x86. You normally do not need to choose Run as administrator.
Screenshot needed
Windows Start menu showing PowerShell.
When PowerShell opens, you should see something similar to:
PS C:\Users\YourName>
Your actual Windows username will appear instead of YourName.
This line means PowerShell is ready for your next instruction.
Do not type the PS C:\Users\YourName> portion yourself. You will paste commands after it.
I have never used PowerShell beforeLearn more
PowerShell does not always give you the visual confirmation you might expect from a normal application.
Some commands display many lines of information. Others finish successfully and display almost nothing.
In most cases, when you see the normal prompt again:
PS C:\Users\YourName>
PowerShell has finished the previous command and is waiting for another one.
You do not have to guess whether the important parts of this setup worked. We provide a verification command after each major step.

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

Step 2 · Install Node.js

The testRigor CLI requires Node.js version 18 or newer.
You will not normally open Node.js yourself. It provides functionality that the testRigor CLI needs.
First, check whether Node.js is already installed:
node --version
If you see a version number of 18 or newer, Node.js is already installed.
Now run:
npm --version
You should see another version number.
If Node.js is not installed, go to the official Node.js website and download the current LTS version for Windows.
LTS means Long-Term Support. It is generally the stable version intended for normal use.
Run the installer and keep the default installation options unless your organization has provided different instructions.
When installation finishes, close PowerShell completely and open it again, then run the version commands above again.
✓ Checkpoint — Continue when both node --version and npm --version return version numbers.
npm says that running scripts is disabledTroubleshooting help
You may see an error similar to:
npm.ps1 cannot be loaded because running scripts is disabled on this system
This does not necessarily mean Node.js failed to install. Windows may simply be blocking the PowerShell script used by npm.
First try:
npm.cmd --version
If this returns a version number, npm itself is installed correctly.
You can use npm.cmd instead of npm when installing the testRigor CLI later:
npm.cmd install -g @testrigor/testrigor-cli
Another option, if your organization’s security policy permits it, is:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
If this is a company-managed computer and you are unsure whether you are allowed to change this setting, use the npm.cmd option or contact your IT team instead.

Step 3 · Check for Git

Git will be used later to download the testRigor Skills.
You do not need to learn Git for this setup.
First, check whether Git is already installed:
git --version
If you see a Git version number, Git is already installed. Do not reinstall it.
If PowerShell says that git is not recognized, download and install Git for Windows.
After installation, close PowerShell, open it again, and run:
git --version
✓ Checkpoint — Continue when git --version returns a version number.

Install:
Add the testRigor CLI

Step 4 · Install the testRigor CLI

CLI means Command-Line Interface.
It is another way of interacting with testRigor: instead of clicking a button in the web application, a command can perform the operation.
In PowerShell, run:
npm install -g @testrigor/testrigor-cli
You may see several lines while npm downloads and installs the 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 still gives me the scripts-disabled errorTroubleshooting help
Use:
npm.cmd install -g @testrigor/testrigor-cli
instead.
Then verify normally:
testrigor --version

I already had the testRigor CLI installedTroubleshooting help
If an older installation already exists, update it with:
npm install -g @testrigor/testrigor-cli@latest
Then check:
testrigor --version
If Windows still appears to be using an unexpected installation, run:
where.exe testrigor

Connect:
Give Cursor Access to testRigor

Step 5 · Create a testRigor Personal Authentication Token

Cursor needs permission to communicate with your testRigor account through MCP.
testRigor provides this through a Personal Authentication Token, or PAT.
Think of the PAT as a special password created for tools that need to communicate with testRigor.
In testRigor:
  1. Click your username in the upper-right corner.
  2. Select API Tokens.
  3. Click Generate New Token.
  4. Give the token a clear description, such as Cursor.
  5. Choose an expiration that follows your organization’s security policy.
  6. Generate the token.
  7. Copy it.
Screenshot needed
testRigor API Tokens page.
Screenshot needed
Generate New Token screen with the token named Cursor.
Keep this token available. You will use it to authenticate the testRigor CLI and to configure the MCP connection in Cursor.
Treat the PAT like a password. Do not include it in screenshots, public messages, documentation, or source-control repositories.
If a token is accidentally exposed, revoke it in testRigor and generate a new one.

Step 6 · Authenticate the testRigor CLI

Now we will use the Personal Authentication Token you just created.
In PowerShell, run:
testrigor authenticate
The CLI will ask for your testRigor Personal Authentication Token.
Paste the PAT and press Enter.
Once the token is saved, the CLI will display a confirmation message.
This allows future CLI commands to authenticate without asking you to enter the token every time.
✓ Checkpoint — Continue when the CLI confirms that authentication was saved.

Step 7 · Open Cursor’s MCP Configuration

Now we will use the same Personal Authentication Token to connect Cursor directly to testRigor.
MCP stands for Model Context Protocol.
You do not need to understand the protocol itself. For this setup, the important idea is: MCP allows Cursor to communicate directly with testRigor.
Open Cursor.
Go to:
Customize → MCPs
From there, choose the option to add a new MCP configuration.
Cursor will open the configuration file where MCP servers are defined.
Screenshot needed
Cursor Customize → MCPs screen showing the option to add a new MCP.

Step 8 · Add the testRigor MCP Server

Paste the following configuration into the MCP configuration file:
{
  "mcpServers": {
    "testrigor": {
      "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 in testRigor.
Do not leave the words YOUR_TESTRIGOR_PAT in the configuration. They are only a placeholder.
Save the configuration file.
After saving, return to Cursor’s MCP settings.
Screenshot needed
Cursor MCP configuration file containing the testRigor MCP configuration, with the real token hidden or blurred.
✓ Checkpoint — Continue when testRigor appears in Cursor as a configured MCP server.

Step 9 · Confirm the MCP Connection

Once the MCP configuration is saved, Cursor should display testRigor in the list of available MCP servers.
You should also be able to see the tools provided by the testRigor MCP server.
Screenshot needed
Cursor showing the testRigor MCP server and its available tools.
Give the connection a simple test. Start a new Agent chat in Cursor and try a read-only request:
List the testRigor test suites I have access to.
Cursor should use the MCP connection to retrieve the test suites available to the testRigor user who generated the PAT.
✓ Checkpoint — If Cursor can retrieve your test suites, Cursor and testRigor are successfully communicating through MCP.
Cursor connects to testRigor but cannot access my suiteTroubleshooting help
Open the same suite in the testRigor web application while signed in as the user who generated the PAT.
If that user cannot access the suite in testRigor, the PAT will not provide additional access through MCP.
MCP does not bypass testRigor permissions. Correct the testRigor access problem first.

Add the Skills:
Teach Cursor How to Work with testRigor

Step 10 · Understand the testRigor Skills

MCP gives Cursor access to testRigor.
Skills give Cursor more detailed instructions about how to work with testRigor correctly.
A Skill is not another application. There is no separate testRigor Skills login screen or application icon.
Skills are instruction files stored on your computer that Cursor can use when your request involves testRigor.
🔁
testrigor-dev-loop
The end-to-end workflow
Helps Cursor build, run, inspect, fix, and run tests again as part of an iterative development loop.
✍️
testrigor-write-tests
Writing testRigor tests
Helps Cursor write and edit testRigor tests, reusable rules, and other testRigor test content.
⌨️
testrigor-cli
Using the CLI
Helps Cursor understand and use testRigor command-line functionality correctly.

Step 11 · Download the testRigor Skills

Return to PowerShell.
Download the Skills repository:
git clone https://github.com/TestRigor/skills.git "$HOME\testrigor-skills"
You will probably see messages such as:
Cloning into...
Receiving objects...
Resolving deltas...
When the normal PowerShell prompt returns, the files have been downloaded.
The testrigor-skills folder already existsTroubleshooting help
This usually means the Skills were downloaded during an earlier setup attempt.
You do not need to delete everything and start again.
Update the existing copy with:
git -C "$HOME\testrigor-skills" pull
Then continue with the steps below.

Step 12 · Create Cursor’s Agents Skills Directory

For Cursor, the Skills need to be placed in the appropriate Agents directory.
Create the Skills folder:
New-Item -ItemType Directory -Path "$HOME\.agents\skills" -Force | Out-Null
You may see no success message at all. That is normal.
Important: The directory is .agents with Agents in the plural. Some instructions for other AI coding agents use different directories.

Step 13 · Copy the testRigor Skills into Cursor

Run:
Copy-Item -Path "$HOME\testrigor-skills\testrigor-*" -Destination "$HOME\.agents\skills" -Recurse -Force
PowerShell may display little or no output.
Instead of guessing whether it worked, verify it:
Get-ChildItem "$HOME\.agents\skills" -Directory -Filter "testrigor-*"
You should see:
testrigor-cli
testrigor-dev-loop
testrigor-write-tests
✓ Checkpoint — Continue when the three testRigor Skill folders appear.
Another guide uses a Claude Skills directoryLearn more
Different AI coding agents may use different locations for Skills.
For this Cursor setup, use:
$HOME\.agents\skills
Do not copy the Claude-specific Skills path when following this guide.

Step 14 · Restart or Reload Cursor

If Cursor was open while the Skills were installed, restart or reload Cursor.
After restarting, go to:
Customize → Skills
You should now see the testRigor Skills listed there.
For example, you should be able to see:
testrigor-cli
along with the other installed testRigor Skills.
Screenshot needed
Cursor Customize → Skills screen showing the installed testRigor Skills.
✓ Checkpoint — Continue when the testRigor Skills appear under Customize → Skills.

Start Working:
Use Cursor with testRigor

Step 15 · Start a New Cursor Chat

At this point, Cursor has access to the testRigor MCP server, the testRigor CLI is installed, and the testRigor Skills are available.
Start a new Agent chat in Cursor.
You can now describe what you want to accomplish in normal language.
For example:
List my testRigor test suites.
Or:
Help me write a testRigor test for a user logging into my application and verifying that the dashboard appears.
Or:
Run my testRigor tests and help me troubleshoot any failures.
Depending on the task, Cursor can use the testRigor MCP connection, CLI, and Skills as part of the workflow.

Setup Complete:
You’re Ready to Use Cursor with testRigor

At this point, the core setup is complete.
✓ Cursor
Your AI coding agent is ready to work with the testRigor integration.
✓ testRigor CLI
Installed and authenticated with your testRigor account.
✓ MCP
Cursor can communicate directly with testRigor.
✓ testRigor Skills
Cursor has testRigor-specific guidance available when you ask it to work with tests.
For normal use, your workflow is now much simpler:
  1. Open Cursor.
  2. Start a new Agent chat.
  3. Describe what you want to accomplish in normal English.
  4. Review Cursor’s proposed actions.
  5. Verify the result in testRigor.
Why all three components? The CLI, MCP server, and testRigor Skills serve different purposes. Together, they provide Cursor with the complete testRigor integration needed to work as intended.

Troubleshooting:
If Something Doesn’t Look Right

If your setup worked normally, you do not need to read everything below. Open only the problem that matches what you are seeing.
node is not recognizedTroubleshooting help
If you just installed Node.js, close PowerShell completely and open it again.
Then run:
node --version
Do not immediately reinstall Node.js. An already-open PowerShell window may simply not know about the new installation yet.

npm.ps1 cannot be loaded because scripts are disabledTroubleshooting help
Try:
npm.cmd --version
If that works, npm itself is installed.
Use:
npm.cmd install -g @testrigor/testrigor-cli
when installing the testRigor CLI.
If your organization’s policies allow it, another option is:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Do not weaken or bypass company-managed security policies without approval.

git is not recognizedTroubleshooting help
Install Git for Windows, then close and reopen PowerShell.
Check again with:
git --version

I ran a PowerShell command and nothing appearedTroubleshooting help
Some PowerShell commands do not display a success message.
If the normal prompt returns:
PS C:\Users\YourName>
the command has probably finished. Use the verification step immediately after the command rather than guessing whether it worked.

A folder or item already existsTroubleshooting help
This often means part of the setup was already completed during an earlier attempt.
Do not automatically delete the existing folder.
For the testRigor Skills repository, update the existing copy with:
git -C "$HOME\testrigor-skills" pull

testRigor does not appear in Cursor’s MCP listTroubleshooting help
First, confirm that you saved the MCP configuration file.
Then check whether:
  • The JSON configuration is valid.
  • The MCP URL is https://api2.testrigor.com/api/v1/mcp.
  • The header name is personal-access-token.
  • The full PAT was copied correctly.
  • The PAT is still valid and has not been revoked.
Restart or reload Cursor after correcting the configuration.

Cursor can connect to testRigor but cannot access my suiteTroubleshooting help
Open the same suite in the testRigor web application while signed in as the user who generated the PAT.
If that user cannot access the suite in testRigor, MCP will not provide additional permissions.
Correct the testRigor access problem first.

Cursor does not show the testRigor SkillsTroubleshooting help
In PowerShell, check:
Get-ChildItem "$HOME\.agents\skills" -Directory -Filter "testrigor-*"
You should see:
testrigor-cli
testrigor-dev-loop
testrigor-write-tests
If the folders are present, close Cursor completely and start it again.
Then return to Customize → Skills.

Next Steps:
Go Further with Cursor and testRigor

Once the initial setup is working, you can explore more advanced workflows such as testRigor CLI execution options, CI/CD usage, localhost testing, targeted test execution, JUnit reporting, synchronizing local test files, and using Cursor to help create and troubleshoot testRigor tests.
For more information, see:
Your actual instructions to Cursor can still be written in plain English.
Automate tests with plain English using Generative AI. Reduce QA overhead, increase coverage, efficiency and scalability.
Get Our Newsletter
We will send monthly testRigor updates on new features, upcoming events and links to recordings.
Email*
Product
Company
Security
Resources & Learning
© 2026 testRigor. All rights reserved.
Privacy Overview
This site utilizes cookies to enhance your browsing experience. Among these, essential cookies are stored on your browser as they are necessary for ...
Read more
Strictly Necessary CookiesAlways Enabled
Essential cookies are crucial for the proper functioning and security of the website.
Non-NecessaryEnabled
Cookies that are not essential for the website's functionality but are employed to gather additional data. You can choose to opt out by using this toggle switch. These cookies gather data for analytics and performance tracking purposes.