Use QA Wolf from coding agents to request test coverage, run flows, inspect results, and drive a cloud browser. One shared skill supplies the workflow; client adapters and MCP settings supply the tools.
This is an API-key preview, not an approved listing in the providers' official directories. Connect to https://app.qawolf.com/api/mcp with your QA Wolf API key. Installing the plugin does not authenticate your connection. OAuth sign-in is not yet supported.
See the platform setup guide for native plugins, separately configured MCP clients, and guidance-only limitations. Do not assume that an instruction file exposes QA Wolf tools.
Get a team API key from QA Wolf. Configure it outside chat through the client's secure credential input or launch environment, normally as QAWOLF_API_KEY. Do not put the key in shell history, source control, a prompt, or a public issue. Desktop clients need the credential in the process that actually starts their MCP connection.
/plugin marketplace add qawolf/agent-plugins
/plugin install qawolf@qawolf
codex plugin marketplace add qawolf/agent-plugins
codex plugin add qawolf@qawolfcopilot plugin marketplace add qawolf/agent-plugins
copilot plugin install qawolf@qawolfgemini extensions install https://github.com/qawolf/agent-pluginsEnter the API key only in Gemini's sensitive extension-setting prompt.
pi install git:github.com/qawolf/agent-pluginsThis installs the skill, not an MCP bridge. Pi users need a separately reviewed MCP extension configured for QA Wolf.
Review the third-party installer before running it, then select your client.
npx skills add qawolf/agent-plugins --skill qawolfMCP setup is separate unless the client reads a bundled MCP adapter. Amp reads the skill's mcp.json; other clients should follow the platform guide. That guide also covers native installs for Grok, Devin, Qoder, and Hermes, plus manual MCP setup and clients without a verified QA Wolf tool connection.
Restart the client or start a fresh session, then call whoami and confirm the account and workspace. For onboarding, require both agent_send and agent_get. Share the returned session URL; acceptance does not mean the flow is finished. Browser runners bill while they exist, so terminate them when work ends.
If your client uses AGENTS.md, append its QA Wolf section rather than replacing your project's existing instructions.
- "Ask QA Wolf to cover the checkout journey in this repository."
- "Run the smoke-tagged QA Wolf flows and summarize what failed."
- "Open a QA Wolf browser and reproduce the login bug."
See the plugin guide for authentication requirements and troubleshooting.
Review requested actions before approving them. Tool arguments and results can include test data, environment values, and browser screenshots. Never include credentials or customer test data in public reports.