> ## Documentation Index > Fetch the complete documentation index at: https://www.minitap.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Every tool Minitap connects to, what Mini does with each one, and where to set it up. Mini works in the tools your team already uses: it builds from your repository, posts on your pull requests and in Slack, reads your tickets and specs, and files what it finds in your tracker. This page lists every integration and how far each one goes, so you can pick the ones worth connecting. Connect them from **Settings → Integrations**. Connecting a repository, Linear or Jira takes a workspace owner or admin. ## Code and CI | Integration | What Mini does with it | Docs | | - | - | - | | **GitHub** | Builds your app from any commit and keeps the scenarios in step with your code. Comments on pull requests to your main or release branches with a box to tick to run the tests, answers `@mini test`, and posts a check named after your app on every run. The check informs by default; turn on **Block merge on failing tests** and branch protection can require it. | [GitHub](https://www.minitap.ai/docs/minitest/integrations/github.md), [Pull request checks](https://www.minitap.ai/docs/minitest/runs/pull-request-checks.md) | | **GitHub Action** | Starts a run from any workflow, signed in with GitHub OIDC. Uploads your build or asks Mini to build the commit, picks the browsers for web runs, and can wait for the verdict to hold a release. On a release tag, runs only the scenarios affected since the previous tag. | [GitHub Action reference](https://www.minitap.ai/docs/minitest/reference/minitest-trigger-action.md) | | **CLI, for any CI** | GitLab CI, CircleCI, Jenkins, Azure Pipelines and Bitbucket Pipelines run Mini through the CLI with a workspace API key. It uploads your `.ipa`, `.apk`, `.apks` or `.aab`, starts runs, and reads every verdict as JSON. | [Ways to start a run](https://www.minitap.ai/docs/minitest/runs/triggering-a-run.md#cli-for-any-ci) | | **GitLab and Bitbucket** | Connect a GitLab group (self-hosted too) or a Bitbucket workspace: Mini builds from your repositories and keeps the scenarios in step with your code. Comments and checks on pull requests are GitHub only; gate a pipeline through the CLI. | [GitHub](https://www.minitap.ai/docs/minitest/integrations/github.md#gitlab-and-bitbucket) | | **TestFlight** | Add Minitap's tester to TestFlight once, paste a build's link, and Mini runs that build on physical iPhones, where your workspace has them. | [Upload a build](https://www.minitap.ai/docs/minitest/setup/upload-a-build.md) | ## Where your team talks | Integration | What Mini does with it | Docs | | - | - | - | | **Slack** | Posts one message per run and edits it as the run goes. Each issue gets a thread with a clip of the failure and **Acknowledge**, **Not a bug** and **Resolved** buttons. A scheduled run posts one summary. Start runs with `@mini run`, and Mini asks in the channel when it needs context or a test account. | [Mini in Slack](https://www.minitap.ai/docs/minitest/integrations/mini-in-slack.md) | ## Tickets and specs | Integration | What Mini does with it | Docs | | - | - | - | | **Jira** | Reads your tickets, their comments, attachments and test cases for context. Mention `@Mini` in a Jira comment and it tests the ticket, then replies there with the report, the recording and the scenario. Files a ticket from an issue, a UI/UX suggestion or a failed criterion, or links a ticket you already have. | [Jira](https://www.minitap.ai/docs/minitest/integrations/jira.md) | | **Linear** | Files a Linear issue from an issue, a UI/UX suggestion or a failed criterion, with the steps to reproduce and the recording. Or links the issue you already have, and its status shows beside the finding. | | | **Notion** | Reads the specs and PRDs your team already wrote, and writes scenarios from them. Sends a finding to a Notion database as a new page, or links a page you already have. | | | **Figma** | Opens the designs linked in your tickets, so Mini knows what the screen should look like. | | ## Coding agents | Integration | What Mini does with it | Docs | | - | - | - | | **MCP server** | Your coding agent in Cursor, Claude Code or Windsurf signs in to Minitap's MCP server. It can read and edit scenarios, test accounts and builds, start runs and read their results. | [Coding agents](https://www.minitap.ai/docs/minitest/integrations/cursor-and-claude.md) | | **Fix prompts** | Every failed criterion has a fix prompt: the root cause, the steps to reproduce and a proposed fix, ready to paste into your coding agent. The CLI ships a skill so the agent can run Mini itself. | [Fix prompt](https://www.minitap.ai/docs/minitest/runs/run-report.md#fix-prompt) | ## What Mini gets access to * **GitHub**: the repositories you pick when you install the Minitap GitHub App. * **Slack**: Mini joins your public channels and posts each run to the channel you pick. Anything started from Slack runs as that person's own Minitap account. * **Jira, Linear and Notion**: Mini reads what you connect, and writes only the tickets you send and its replies to `@Mini`. * **CLI and MCP server**: a workspace API key or your own sign-in. For how Minitap handles your data, see [Security](https://www.minitap.ai/docs/minitest/workspace/security.md). ## Next steps > [card] [Install the GitHub App](https://www.minitap.ai/docs/minitest/integrations/github.md) > > Builds from your repository, and Mini on your pull requests. > [card] [Connect Slack](https://www.minitap.ai/docs/minitest/integrations/mini-in-slack.md) > > Live runs in a channel, and runs started from a message. > [card] [Mini on Jira](https://www.minitap.ai/docs/minitest/integrations/jira.md) > > Tickets with the recording, and `@Mini` in any comment. > [card] [Connect your coding agent](https://www.minitap.ai/docs/minitest/integrations/cursor-and-claude.md) > > The MCP server and the CLI for Cursor and Claude Code. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.