> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/getting-started/integrating-mcp-servers/linear.md).

# Linear

This guide walks through connecting Linear to DuploCloud — registering the Linear MCP server, creating a provider with your Linear API key, and querying Linear data through the AI agent.

It covers the Linear-specific values you need. For the general mechanics of MCP servers, providers, credentials and scopes, see [MCP Servers](/docs/armor/mcp-servers.md).

***

## Step 1 — Generate a Linear API Key

In Linear, open the workspace menu (top-left) and click **Settings**.

![Linear settings menu](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-4d84cafa1637b3f8056a0c2090b6e33f1bd6e7a4%2Flinear-step-01.png?alt=media)

Navigate to **Security & access** in the left sidebar. Scroll down to the **Personal API keys** section and click **New API key**. Give it a name, click **Create**, and copy the generated key — it is only shown once.

![Personal API keys section with key created](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-9a37e4442b86723798be13a943620a4885af7910%2Flinear-step-02.png?alt=media)

***

## Step 2 — Register the Linear MCP Server

In DuploCloud, go to **AI Admin → MCP Servers** and click **+ Add MCP Server**.

![MCP Servers list](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-6a4eeb5dd66ad68f09cf5d92ef08d1a71920b5ac%2Fduplocloud-linear-step-01.png?alt=media)

Fill in the **Basic** section:

* **Name** — e.g. `Linear`
* **Provider Type** — select **Other**
* **Config Type** — **HTTP/SSE**
* **API Endpoint** — `https://mcp.linear.app/mcp`
* **Transport** — `http`

![Add MCP Server form](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-b4e14f347340412d11836113b678f599f73eb499%2Fduplocloud-linear-step-02.png?alt=media)

Click **Create**. (The **Metadata** section is optional — see [Registering an MCP server](/docs/armor/mcp-servers.md#stage-1-register-the-mcp-server).)

***

## Step 3 — Create the Provider, Credential and Scope

Go to **AI Admin → Providers**, select the **Other** tab, and click **+ Add Provider**. The page walks through three sections in order — Provider Details, Credentials, and Scope — described in full under [Create the Provider, credential, and Scope](/docs/armor/mcp-servers.md#stage-2-create-the-provider-credential-and-scope).

Use these values for Linear:

**Provider Details**

* **Name** — e.g. `Linear`
* **Type** — **Other**
* **Account ID** — any identifying label; Linear does not require a specific account ID

**Credentials**

* **Name** — e.g. `Linear-credentials`
* **Key** — `LINEAR_API_KEY` (the only accepted key name for Linear credentials)
* **Value** — the API key copied from Linear in Step 1

**Scope**

* **Name** — e.g. `Linear-Test-MCP`
* **MCP Server** — the Linear server registered in Step 2
* **Resource Map** — add two keys:
  * `Authorization` → your Linear API key value. The key name is case-sensitive; use `Authorization` exactly as written
  * `type` → `http`

The credential created in the previous section is carried forward automatically. Click **Create**, then choose which workspaces the scope should be available to.

***

## Step 4 — Use Linear in a Ticket

Go to **AI DevOps → HelpDesk → Add Ticket** and select your Linear scope from **Select Scopes**.

![Selecting the Linear scope in a ticket](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-b908cdc303f8b45399e099f2cb836bb61361da54%2Fduplocloud-linear-step-08.png?alt=media)

Describe what you want — for example, asking the agent to list your issues.

![Ticket with Linear prompt entered](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-562ba1ecf6d54f81aa2028e196a86afe162c39a7%2Fduplocloud-linear-step-09.png?alt=media)

Submit the ticket. The agent connects to Linear through the MCP server and returns the results, calling tools named `mcp__Linear__<tool>` using the credentials bound to the scope.

{% hint style="info" %}
By default the agent asks before running any MCP tool. To let Linear's tools run without prompting on a given ticket, set that under **MCP Tool Permissions** in the ticket's Details panel — see [Controlling which tools the agent may call](/docs/armor/mcp-servers.md#controlling-which-tools-the-agent-may-call).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/getting-started/integrating-mcp-servers/linear.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.