# Linear

> Canonical: https://www.yalc.ai/mcps/linear/

Project management for GTM ops, surfaced inside Claude Code via the Linear MCP.

## Categories

- operations

**Website:** https://linear.app/

**Repo:** https://github.com/jerhadf/linear-mcp-server

## Glance

- Auth: Linear API key
- Maintainer: Community
- Tools: Issues + projects + teams

**Install Command:** claude mcp add linear --env LINEAR_API_KEY=lin_api_xxx -- npx -y @jerhadf/linear-mcp-server

**Install Notes:** Generate an API key at linear.app/settings/account/security. Replace `lin_api_xxx` with your key, run the command, restart Claude Code. Multiple community Linear MCP packages exist; pick one and stick with it.

**Yalc Fit Score:** 6

**Yalc Verdict:** Useful when GTM ops actually live in Linear (less common than Notion or Asana). For most Yalc operators, Notion is the better project tracking surface.

## Plain Description

Linear's API exposes issues, projects, cycles, teams, and labels. The community Linear MCP servers wrap that API as native Claude tool calls. Auth is a personal API key, simpler than OAuth.

For Yalc workflows, Linear fits when the team already runs all ops there. Common pattern: engineering teams using Linear for product work, with GTM ops piped in as a separate "GTM" team or project. The MCP lets Yalc create issues for content production, track campaign launch milestones, and surface blocked work without leaving Claude Code.

## Yalc Framework

**Workflow Step:** route

### Workflow Narrative

The Linear MCP sits at the **route** node when Linear is the team's source of truth for tasks and milestones. Less common in pure GTM teams (Notion or Asana usually wins) but useful when the team is engineering-heavy.

Most useful patterns: open issues for content briefs that need writing, track campaign launch dependencies, surface blocked engineering work that affects GTM timelines.

**Workflow Position:** The task and project tracking node, when Linear is the system of record. Yalc reads issue states, creates issues with structured descriptions, and updates statuses as work progresses.

### Prompt Patterns

- Yalc, for the "Q3 outbound launch" project in Linear, list every issue not done. Group by team, surface blockers older than 5 days, post a digest to #project-launch Slack.
→ Yalc reads Linear issues, classifies, posts via Slack MCP.

- Yalc, this Notion brief is approved. Open Linear issues for each deliverable: copy the brief sections, assign to the right team member, set due dates from the timeline.
→ Yalc parses Notion, creates Linear issues with full structured content.

- Yalc, give me a velocity snapshot for the GTM team this cycle. Issues completed, in progress, and at risk based on due-date proximity.
→ Yalc reads cycle data, computes via Claude, returns digest.


### Chaining

**Upstream:** Notion brief or campaign plan → Linear MCP (create issues)

**Downstream:** Linear issue completion → Yalc workflow (notify, update CRM, post to Slack)


### Anti Patterns

- Don't use Linear as a CRM. It's for tasks, not customer relationships. Notion or HubSpot for CRM.
- Don't dual-write tasks to Linear and another tool. Pick one source of truth.
- Don't create issues without a clear assignee and due date. Linear issues without owners go stale fast.


**Compatibility:** Multiple community Linear MCP packages exist, all with similar surfaces. Works in Claude Code, Claude Desktop, Cursor. Linear's API has standard rate limits.

## Pros

- Linear's API is well documented and stable.
- API key auth is simpler than OAuth for personal use.
- Coverage of issues, projects, cycles, teams, labels is comprehensive.
- Free for individual use; team plans scale predictably.
- Pairs cleanly with Notion (briefs) and Slack (notifications).

## Cons

- GTM teams often don't use Linear; default to Notion or Asana for ops.
- Multiple competing community MCPs. Picking one is friction.
- Linear's hierarchy (team > project > issue) requires upfront structure to be useful.
- Less mature MCP ecosystem than Notion or Slack.

## Who For

- Engineering-heavy GTM teams running ops in Linear
- Product-led growth teams where engineering and GTM share a tool
- Operators who want to bridge Notion (briefs) and Linear (execution)

## Related

### Mcp

**Rule:** Use Notion for briefs and CRM, Linear for execution tracking.

**Url:** /mcps/notion/



## Alternatives

- **Notion MCP**
  - Rule: Default for most GTM teams. More flexible, broader use cases.
  - Url: /mcps/notion/
- **Asana MCP (community)**
  - Rule: Switch when Asana is the team's project tool.
  - Url: #
- **Direct Linear API**
  - Rule: Skip the MCP for headless cron jobs. Direct API is more efficient.
  - Url: #

## Faq

- Q: Should I use Linear for GTM ops?
  - A: Only if your team is already on Linear for engineering. Greenfield GTM teams should default to Notion. Linear is more rigid; Notion is more flexible for the messy data structures GTM ops need.
- Q: Which community Linear MCP should I install?
  - A: As of April 2026, `@jerhadf/linear-mcp-server` is the most actively maintained. Check GitHub last-commit dates before installing; abandoned community packages are common.
- Q: Can the MCP create projects, not just issues?
  - A: Yes. Most community MCPs cover the project create/update endpoint. The hierarchy goes team to project to issue, with cycle as a parallel grouping.
- Q: How does this interact with Linear's GitHub integration?
  - A: Linear can auto-link Git commits to issues when configured. The MCP doesn't change that integration; Linear handles it server-side.
- Q: Can the MCP trigger Linear automations?
  - A: Yes via the standard issue update verbs. Linear's automations fire on state transitions; the MCP can update state, which triggers any configured workflows.
- Q: Is the Linear MCP free?
  - A: The MCP package is free (open source). Linear itself charges per seat above the free tier. Yalc workflows that read existing data work on Linear's free plan.

**Reviewer:** Othmane Khadri