# Linear

> Manage Linear issues, projects, and cycles from AI context.

[Canonical HTML page](https://top-mcps.com/mcp/linear) · [server.json](https://top-mcps.com/mcp/linear.json) · [methodology](https://top-mcps.com/about/methodology)

## At a glance

- **Maintainer:** Linear
- **Transport:** SSE, Streamable HTTP
- **Auth model:** OAuth 2.1
- **Required secrets:** LINEAR_API_KEY
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Linear workspaces
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-31
- **Score:** 53/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/linear/linear-mcp-server

## Security & scope

- **Access scope:** read-write
- **Sandbox:** OAuth 2.1 against the authenticated Linear user; the agent acts as that user. Scope is whatever the OAuth grant was approved for.
- **Gotchas:**
  - Issues created by the agent appear under your Linear identity, not an "agent" identity.
  - Be explicit about team / project in prompts — the agent picks defaults silently otherwise.

## Quick answer

**What it does.** Provides access to Linear projects, issues, cycles, teams, and comments via the Linear API.

**Best for:**
- Bug-to-issue creation
- Project status updates
- Sprint planning
- Issue triage
- Development workflow tracking

**Not for:**
- Non-Linear project management
- Large enterprise Jira workflows

## Recipes

### Create a well-formed Linear issue

```
Create a Linear issue in the `Engineering` team with title "Follow up on MCP redesign review", label `backend`, priority medium, and due date this Friday. Include a short description pointing to the GitHub PR URL I will paste after you confirm.
```

_Tested with: Claude Desktop, Cursor_

## Description

The Linear MCP connects AI models to your Linear workspace, enabling issue creation, project management, and cycle planning directly from AI conversations. Eliminate context switching between your AI tools and project management.

## Why it matters

Developers using Linear spend time switching between AI tools and project management. This MCP removes that friction.

## Key features

- Issue CRUD operations
- Project and cycle management
- Team and member access
- Label and priority management
- Linear API integration

## FAQ

### Does it need a Linear API key?

Yes. Generate one at linear.app/settings/api and set `LINEAR_API_KEY` in the MCP env block. Linear also supports OAuth 2.1 for multi-user deployments, but the MCP accepts a plain personal API key for single-user agent use.

### Can it create issues automatically?

Yes. The typical flow: the agent finds a bug while editing code, calls `create_issue` with the failing file/line, and the issue lands in your Triage inbox with the code snippet in the description. Label and priority are settable at creation.

### Does it handle cycles and sub-issues?

Yes. It can attach issues to a cycle, create parent/child issue relationships, and move sub-issues between parents. That lets the agent break down a large story into scoped tasks without manual triage.

### Can it read comments and resolve discussions?

It reads comments via `list_comments` and can post new ones via `create_comment`. It cannot mark a comment as "resolved" — that is a Linear UI action without an API equivalent.

### Will it respect team permissions?

Yes. The API key inherits your Linear user's permissions, so the agent can only see teams and issues you have access to. For shared agent deployments, create a dedicated "Agent" user with a scoped role so humans and agents show up separately in audit logs.

## Changelog

- **2026-05-31** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-02-15** — Initial directory listing.