> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qa.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Linear

> Connect Linear Agent to QA.tech MCP, and let the QA.tech assistant search and create Linear issues

Use Linear with QA.tech in two agent directions:

* **Linear Agent** can call QA.tech tools after you add the [QA.tech MCP server](https://docs.qa.tech/integrations/mcp.md). Ask about test cases, runs, and issues without leaving Linear.
* The [AI Chat Assistant](https://docs.qa.tech/core-concepts/ai-chat-assistant.md) can search and create Linear issues once you connect Linear in QA.tech.

You can also manually export a detected test issue to Linear. Issues are **not automatically synced**.

## Connect QA.tech MCP in Linear

Add the QA.tech MCP server as a custom connection so Linear Agent can list tests, inspect runs, and look up QA.tech issues.

The MCP endpoint is:

```
https://api.qa.tech/v1/mcp
```

Use OAuth when Linear offers it (URL only, no headers). Sign in to QA.tech, pick an organization, and optionally limit the grant to specific projects. You only see data you already have permission to view.

**1. Allow MCP in the Linear workspace**

A workspace owner or admin must enable MCP servers in Linear. Open
[Workspace settings → Security](https://linear.app/settings/security), turn
**Enable MCP servers** on, and either allow all servers or allow this custom
URL. Linear documents the workspace and member flows in [Connect MCP Servers
to Linear Agent](https://linear.app/docs/connect-mcp-servers).

**2. Add a custom server**

In Linear, open **Settings → Agent personalization**
([linear.app/settings/account/agents](https://linear.app/settings/account/agents)).
Under **MCP servers**, click **+**, then **Custom URL**. Paste
`https://api.qa.tech/v1/mcp`.

**3. Sign in to QA.tech**

Complete the OAuth flow in the browser. Return to Linear and confirm the
server shows as connected.

If Linear cannot complete OAuth, use an API key instead. Create a key under **Organization Settings → API Keys** in QA.tech, then add an authentication header on the custom server:

```
Authorization: Bearer <API_KEY>
```

Treat the key as a secret. A `read` key lists applications, test cases, runs, and issues. A `write` key can also create test cases and rerun runs. OAuth grants include both `read` and `write`.

Once connected, mention QA.tech in Linear Agent. For the full tool list, see [MCP Server](https://docs.qa.tech/integrations/mcp.md#what-your-assistant-can-do).

> "What failed in the last QA.tech run?"

> "List critical issues QA.tech found this week"

> "Rerun the failed cases from run UkxK"

> [!NOTE]
>
> Linear Agent MCP is not the same as [Custom MCP
> servers](https://docs.qa.tech/core-concepts/ai-chat-assistant.md#custom-mcp-servers) in QA.tech.
> Custom MCP is for pointing the QA.tech chat at *your* MCP servers. This
> section points Linear Agent at QA.tech.

## Using Linear in Chat

Once Linear is connected in QA.tech, the [AI Chat Assistant](https://docs.qa.tech/core-concepts/ai-chat-assistant.md) can search your Linear issues and create new ones from chat.

You can ask the assistant to:

* **Search issues** by keyword or topic
* **Fetch a specific issue** by its key
* **List recent issues** from your connected team
* **Create new issues** with a title and description in your configured Linear team

> "Search Linear for issues related to checkout"

> "Show me DEV-42"

> "What are the most recent issues in Linear?"

> "Create a Linear issue titled 'Fix mobile nav overlap' with a description of the layout bug on small screens"

> [!NOTE]
>
> If you have both Linear and Jira connected, mention which tracker you want
> (e.g. "search **Linear**"). If you do not specify, the assistant defaults to
> Linear when both are configured.

## Connect Linear in QA.tech

This OAuth connection is what chat and issue export use. It is separate from the Linear Agent MCP connection above.

**1. Connect to Linear**

Go to **Settings → Integrations → Linear**. Follow the OAuth flow to grant
QA.tech access to your Linear workspace. The Linear account is shared by
every project in the organization.

**2. Configure the Project**

On the same page, select the **Linear Team** where you want exported issues
to appear, then click **"Save Linear Integration"**.

## Exporting Issues

Once Linear is connected in QA.tech, you can export any detected issue. You can set up the connection with no issues yet, but you need at least one detected issue to export. See [Issues](https://docs.qa.tech/core-concepts/issues.md) for what QA.tech detects.

**1. Open an Issue**

From a test result, open the issue in the **Issues** section. There is no
Issues item in the sidebar.

**2. Click Export**

In the **Link** section, click **"Create issue"**. The issue will be created
in your configured Linear team.

## What Gets Exported

When you export an issue, Linear receives:

* **Title:** The issue title from QA.tech
* **Description:** Includes:
  * Issue type
  * First seen date
  * Issue description
  * Help/hint information (if available)
  * Link back to QA.tech
  * Console error details (for console errors: error level, file location, line numbers, messages)

> [!TIP]
>
> Exported issues include a direct link back to QA.tech, so your team can easily
> access test results and occurrence details.

## Related documentation

* [MCP Server](https://docs.qa.tech/integrations/mcp.md) - connect Claude Code, Cursor, Codex, Continue, or Linear Agent to QA.tech
* [AI Chat Assistant](https://docs.qa.tech/core-concepts/ai-chat-assistant.md) - search and create Linear issues from QA.tech chat
* [Issues](https://docs.qa.tech/core-concepts/issues.md) - detected test issues and manual export


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.