Integrations

QA.tech plugs into
how you already ship

Your tracker, your CI, your chat, your AI tools. 20 integrations that trigger agent test runs and deliver results where your team already works.

20 of 20 integrations

FAQ

Common questions

Does QA.tech integrate with GitHub?
Yes. The GitHub App reviews every pull request automatically: it identifies user-facing changes, creates tests for new functionality, runs them against your preview deployment, and posts a review back on the PR. There is also an API route for triggering test plans from GitHub Actions.
Can I trigger tests from a CI system you don't list?
Yes. Test plans are triggered through a standard REST API keyed off a plan's Short ID, so Bitbucket Pipelines, Azure DevOps, CircleCI, Jenkins, or any system that can make an HTTP request works.
Can I get results in Slack or Microsoft Teams?
Both. Slack gets run-completion alerts in a default project channel with per-run overrides. Teams uses incoming webhooks with a failure-only mode to cut noise.
Does QA.tech work with Jira and Linear?
Yes, in both directions. The agent reads tickets so tests are grounded in the acceptance criteria, and detected issues export back as Jira issues or Linear issues with steps and evidence.
Does QA.tech have an MCP server?
Yes, at api.qa.tech/v1/mcp. It exposes your test cases, runs, and applications to any MCP client, so Cursor or Claude can answer “what runs failed today?” or rerun failed cases. The QA.tech agent can also call your own services through Custom MCP integrations.
Can QA.tech test deployments behind a firewall or Vercel protection?
Yes. There are dedicated setups for Vercel Preview Protection, Vercel WAF, Cloudflare WAF and Turnstile, and IP allowlisting with an SSH proxy tunnel for private networks.

Your team moves fast. Can your testing keep up?

QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.

Get a demo