Connecting testRigor’s MCP Server to Microsoft 365 Copilot

Heather Brooks

This guide walks you through setting up testRigor as a custom federated connector in Microsoft 365 Copilot, enabling you to interact with your test suites, run tests, and review results using natural language directly inside Copilot.

Overview

testRigor’s MCP server exposes your test data as a set of read-only tools. By registering it as a custom federated connector in Microsoft 365 Copilot, you can ask Copilot questions like:

• “List all my test suites in testRigor”
• “What failed in the last regression run?”
• “Show me the execution details for the most recent test case”

Prerequisites

• A testRigor account with access to the API Tokens page
• Global Administrator or AI Administrator role in the Microsoft 365 admin center
• An appropriate Microsoft Entra admin role for SSO authentication
• Access to the Teams Developer Portal: https://dev.teams.microsoft.com

Step 1: Generate a testRigor Personal Access Token

1. Log in to the testRigor app.
2. Click your username in the top-right corner.
3. Select API Tokens.
4. Click Generate a new token.
5. Copy and save the token. You will need it in Step 4.

Step 2: Set Up Authentication in the Teams Developer Portal

Microsoft 365 Copilot requires authentication to be registered before you create the connector. testRigor uses a custom header token, so you will set up an OAuth 2.0 registration and pass the PAT as a bearer-style credential.

Note: If your Microsoft 365 admin has already configured a suitable OAuth registration for testRigor, you can skip to Step 3 and use that registration ID.

1. Go to the Teams Developer Portal: https://dev.teams.microsoft.com
2. Select Tools > OAuth Client Registration.
3. Click + New OAuth connection.
4. Fill in the connection details:

   Field	Value
   Name	testRigor MCP
   Client ID	Use a placeholder or your organization’s client ID
   Client secret	Your testRigor PAT from Step 1
   Authorization endpoint	https://api2.testrigor.com/api/v1/mcp
   Token endpoint	https://api2.testrigor.com/api/v1/mcp

5. Save the registration and copy the Registration ID.

Step 3: Create the Custom Federated Connector in Microsoft 365 Admin Center

1. Sign in to the Microsoft 365 admin center: https://admin.microsoft.com
2. In the left pane, go to Copilot > Connectors.
3. Select the Gallery tab.
4. Under Created by your org, find the Create a new connector tile and click Add.
5. On the Custom connector page, under Connect to MCP server, click Add.
6. Enter the following details:

   Field	Value
   Display name	testRigor
   Base URL	https://api2.testrigor.com/api/v1/mcp

7. Enter the Registration ID from your Teams Developer Portal OAuth setup.
8. Click Save.

Step 4: Roll Out the Connector to Users

1. From the Your Connections list, find the testRigor connector.
2. To deploy to a specific group first, select Stage rollout and choose your target audience.
3. When ready to release broadly, select Deploy to all users.

Note: Changes to a connector can take up to 15 minutes to take effect.

Step 5: Use testRigor in Microsoft 365 Copilot

Viewing test suites and cases

• “List all my test suites in testRigor”
• “Show me the test cases in the [Suite Name] suite”

Running tests

• “Run the regression tests in [Suite Name]”
• “Run only the previously passing tests in [Suite Name]”

Checking results

• “What is the execution status for the last run in [Suite Name]?”
• “Show me all failures from the last test suite run”
• “Get the execution details for [test case name]”

Managing tasks

• “Cancel the task currently running in [Suite Name]”

Available testRigor MCP Tools

Managing the Connector

Need Help?

• testRigor MCP documentation
• Microsoft federated connectors documentation
• For testRigor support, contact your Customer Success Manager.

“We spent so much time on maintenance when using Selenium, and we spend nearly zero time with maintenance using testRigor.”

Keith Powe VP Of Engineering - IDT