Testrigor

com.testrigorPublished by testrigor.comOfficial publisherv1.0.0Updated Oct 25, 2026

Manage test suites, run tests, view results, and automate QA workflows via AI with testRigor.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

A remote testRigor MCP server that lets an assistant manage test suites, run tests, view results and automate QA workflows.

What you can do
Manage test suites: create and organize testRigor test suites through the assistant. Run tests: trigger test executions from the assistant. View results: retrieve and review test run outcomes. Automate QA workflows: let the assistant coordinate testing tasks end to end.
When to use it
Useful when a team already uses testRigor and wants an assistant to drive test suites, start test runs and check results without switching tools. Suited to QA and release workflows where test status needs to be queried or acted on conversationally.
Requirements
A remote endpoint at api2.testrigor.com over streamable HTTP, with no local package. A testRigor account and a Personal Access Token sent in the personal-access-token header, generated from the API Tokens option in the testRigor user menu. Network access to the endpoint.
Before you install
Requires a testRigor Personal Access Token, which grants access to the account's testing resources; keep it secret and scope it carefully. The server can run tests and manage suites, so actions may change test configuration or consume test execution resources.

Installation

In SourceWeft

  1. Open Testrigor in the dashboard and add it to a workspace.
  2. Connect personal-access-token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.testrigor%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "testrigor": {
      "type": "http",
      "url": "https://api2.testrigor.com/api/v1/mcp",
      "headers": {
        "personal-access-token": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.