GitHub Copilot
Use Testery from GitHub Copilot, in the Copilot CLI or in VS Code agent mode. Two pieces work together:
- The Testery plugin gives Copilot skills that run the Testery CLI: create test runs, monitor them, report results, manage environments and schedules, and fix failed runs. It is the same plugin as the Claude Plugin; you don't need a separate package.
- The Testery MCP Server lets Copilot read your Testery data directly: projects, test runs, and test results.
Copilot can then write a test, run it on Testery, and answer questions about the results, without you leaving your editor or terminal.
Prerequisites
- A GitHub Copilot plan. The Free plan works; each prompt uses some of your monthly AI credits.
- The Copilot CLI, or VS Code with Copilot Chat in agent mode.
- A Testery account.
- The Testery CLI on your
PATH, signed in:pip install testerytestery login - Python 3 on your
PATH. The plugin's hooks use it.
Copilot CLI
Install the plugin
Add the Testery marketplace, then install the plugin from it:
copilot plugin marketplace add testery/claude-plugin
copilot plugin install testery@testery
Check that it loaded with copilot plugin list. It should list testery@testery.
Connect the Testery MCP server
copilot mcp add --transport http testery https://mcp.testery.io/mcp
The first time Copilot uses a Testery tool, it opens your browser to sign in to Testery.
Update or remove
copilot plugin update testery
copilot plugin uninstall testery
copilot mcp remove testery
VS Code
Install the plugin
Add the Testery plugin to your user settings.json (Preferences: Open User Settings (JSON)):
{
"chat.plugins.enabled": true,
"chat.plugins.marketplaces": ["testery/claude-plugin"],
"chat.plugins.enabledPlugins": { "testery@testery": true }
}
Open the Chat view, switch to Agent, and check that the testery-* skills are listed under Configure skills.
Connect the Testery MCP server
Add the server to .vscode/mcp.json in your repository, so everyone on the team gets it:
{
"servers": {
"testery": { "type": "http", "url": "https://mcp.testery.io/mcp" }
}
}
Or run MCP: Add Server from the Command Palette, choose HTTP, and enter https://mcp.testery.io/mcp. When VS Code asks, sign in with your Testery account.
Tell Copilot about your project
Copilot reads .github/copilot-instructions.md in your repository. Add your Testery project and environment there, so you don't have to repeat them in every prompt:
## Testery
- Testery project key: `my-web-app`. Default environment: `staging`.
- Use the Testery plugin skills to run, monitor, and report test runs.
Use the Testery MCP tools to answer questions about past runs and results.
- Show results as a short summary line plus a Markdown table.
What you can do
Ask in plain English. Copilot picks the right skill or MCP tool. For example:
- "Run our end-to-end tests on Testery against staging and show me the results."
- "What's my latest Testery test run?"
- "Using the Testery MCP tools, show the results of the latest run as a table."
- "Look at the last 15 runs and tell me which tests never failed and which failed the most."
- "Add a Playwright test for the checkout flow, run it locally, then run the suite on Testery."
You can also call a skill by name, for example /testery-create-test-run or /autofix-failed-test-run. The full list of skills is on the Claude Plugin page.
Copilot has no results widget, so Testery results come back as a Markdown table in the chat.
Pull requests in Azure DevOps and GitHub
Copilot works well with Testery's pull request checks. Copilot writes or fixes a test and pushes a branch; your pipeline runs the suite on Testery; the results come back to the pull request as a status check and, in Azure Pipelines, in the Tests tab. See Azure DevOps, Azure DevOps Pipelines, and GitHub Actions.
Troubleshooting
Copilot says a command was "blocked by an execution hook" or "Denied by preToolUse hook"
- Update the plugin to version 0.1.14 or later (
copilot plugin update testery). Earlier versions ran their hooks through bash, which failed on Windows, and Copilot blocks a tool call when a hook fails. - In VS Code, reload the window (Developer: Reload Window) after updating, so it picks up the new plugin files.
"Redirect URI ... does not match allowed patterns" when signing in to the MCP server
- This was fixed on November 16, 2026. Close the error page and start the sign-in again.
Copilot can't find any Testery tools
- Check that the MCP server is configured and started:
copilot mcp listin the CLI, or MCP: List Servers in VS Code. - In VS Code, the MCP server in
.vscode/mcp.jsonloads only for that folder. Make sure you opened the repository that contains it.
testery command not found, or authentication failures
- Install the CLI with
pip install testery, then runtestery loginandtestery verify-token.