# Integrations – Connect QA.tech to your stack > QA.tech plugs into how you already ship: GitHub, GitLab, any CI, Jira, Linear, TestRail, Slack, Teams, MCP clients, and protected environments. Source: https://qa.tech/product/integrations --- Your tracker, your CI, your chat, your AI tools. 20 integrations that trigger agent test runs and deliver results where your team already works. Filters Plan Build & ship Run & access Report 20 of 20 integrations - [ ### GitHub App→ Automatic AI PR reviews: analyzes changes, writes tests, posts results. Source control & CI/CD ](https://qa.tech/product/integrations/github) - [ ### GitHub Actions→ Trigger test plans and change reviews from GitHub pipelines. Source control & CI/CD ](https://qa.tech/product/integrations/github-actions) - [ ### GitLab→ API-driven CI triggers plus AI merge-request reviews. Source control & CI/CD ](https://qa.tech/product/integrations/gitlab) - [ ### CI/CD REST API→ Trigger test plans from any CI system via REST API. Source control & CI/CD ](https://qa.tech/product/integrations/cicd-api) - [ ### Jira→ Read tickets into test context; export detected issues back. Issue trackers & PM ](https://qa.tech/product/integrations/jira) - [ ### Linear→ Search and create Linear issues from chat; export detected issues. Issue trackers & PM ](https://qa.tech/product/integrations/linear) - [ ### Trello→ Manually export detected issues as Trello cards. Issue trackers & PM ](https://qa.tech/product/integrations/trello) - [ ### TestRail→ Connect your TestRail instance to the QA.tech agent. Test management ](https://qa.tech/product/integrations/testrail) - [![Xray logo](https://qa.tech/assets/xray-BvDYYCst.svg) ### Xray→ Built-in Xray (Jira) test-management connection. Test management ](https://qa.tech/product/integrations/xray) - [ ### Bitrise→ Upload mobile builds and trigger tests from mobile CI. Deployment hooks ](https://qa.tech/product/integrations/bitrise) - [ ### Envoyer→ Trigger tests from Laravel/Envoyer deployment hooks. Deployment hooks ](https://qa.tech/product/integrations/envoyer) - [ ### Slack→ Run-completion alerts to shared or per-run channels. Notifications ](https://qa.tech/product/integrations/slack) - [ ### Microsoft Teams→ Webhook-based run notifications to Teams channels. Notifications ](https://qa.tech/product/integrations/microsoft-teams) - [ ### MCP Server→ Exposes your QA.tech data to external AI clients. AI / MCP ](https://qa.tech/product/integrations/mcp-server) - [ ### Custom MCP Integrations→ Let the QA.tech agent call your own connected services. AI / MCP ](https://qa.tech/product/integrations/custom-mcp) - [ ### Vercel Preview Protection→ Bypass Vercel deployment protection for automation. Environment access & security ](https://qa.tech/product/integrations/vercel-preview-protection) - [ ### Vercel Firewall→ Let QA.tech traffic through Vercel WAF rules. Environment access & security ](https://qa.tech/product/integrations/vercel-firewall) - [ ### Cloudflare WAF & Turnstile→ Handle Cloudflare edge blocking and Turnstile challenges. Environment access & security ](https://qa.tech/product/integrations/cloudflare) - [ ### IP Access Control→ Allowlist QA.tech egress IPs; SSH proxy tunnel for private networks. Environment access & security ](https://qa.tech/product/integrations/ip-access-control) - [ ### Status Badges→ Embeddable pass/fail badge for any test plan. Reporting ](https://qa.tech/product/integrations/status-badges) - ### Don't see your tool? Any CI that can make an HTTP request works with the [CI/CD REST API](https://qa.tech/product/integrations/cicd-api), and anything else can connect over [Custom MCP](https://qa.tech/product/integrations/custom-mcp). Still missing something? [Talk to our team](https://qa.tech/demo) – we'll walk you through the integration roadmap and check whether what you need is already in the works. 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](https://qa.tech/demo)