Enterprise DNAEnterprise DNA

MCP Servers

Linear MCP Server

by Linear

Official Linear MCP server — expose Linear's project and issue tracking APIs as MCP tools for issues, projects, cycles, teams, and comments.

Our verdict

Not reviewed yet

We have not reviewed Linear MCP Server yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About Linear MCP Server

Linear MCP Server is the official server published by Linear that exposes Linear's project and issue tracking APIs as structured MCP tools, giving agents direct read and write access to issues, projects, cycles, teams, and comments inside a Linear workspace. Agents can create, update, triage, and close issues; manage project and cycle state; post and retrieve comments; and search across the workspace — all without leaving the agent session or writing custom API wrappers. The server ships with both stdio and HTTP transports, making it suitable for local Claude Desktop and Cursor setups as well as remote multi-machine deployments. It pairs naturally with the GitHub MCP server to close the full issue-to-PR loop on Linear-led engineering teams, and works best with Claude Desktop, Claude Code, and Cursor as the agent host.

Best for

Linear-first product and engineering teams that want agents to automate issue triage, project tracking, and cycle management across the full Linear workspace

Use cases

  • Triage and assign incoming Linear issues from an agent that reads, labels, and comments automatically
  • Generate weekly cycle summaries and status reports from live Linear data
  • Create and update issues directly from a coding agent when a bug or task is identified
  • Bridge GitHub PR activity back into the correct Linear issue to keep project state in sync
  • Search across projects and teams to surface relevant prior work before starting a new task

Notes

What it does

Linear MCP Server exposes Linear's project and issue tracking APIs as a complete set of MCP-native tools. The core tool surface covers issues (create, update, assign, close, search, list by team or project), projects (create, update, list, retrieve milestones), cycles (list, retrieve active cycle, add issues to a cycle), teams (list, retrieve members and settings), and comments (create, list, retrieve on any issue). Agents get structured JSON responses they can reason over, filter, and act on without parsing raw REST responses.

How to deploy

Add the server to your MCP host config (e.g., claude_desktop_config.json under mcpServers) using the Linear-provided entry point, and set the LINEAR_API_KEY environment variable to a Linear personal API key generated from your workspace settings. For HTTP transport, run the server as a persistent process and point your MCP host at the HTTP endpoint. No additional dependencies or infrastructure are required for the stdio path.

Best practices

Pair Linear MCP with the GitHub MCP server in the same agent session to automate the full engineering workflow: the agent can move a Linear issue from triage to in-progress, open a GitHub branch, and mark the issue complete when the PR merges — all in one loop. Use a dedicated Linear API key scoped to the minimum required permissions, and consider creating a bot user in Linear for agent-driven writes so human and agent activity are clearly separated in the audit log.

Pros

  • Official server — maintained by Linear and kept current with API changes
  • Covers the full issue and cycle workflow end to end including comments and team management
  • HTTP transport enables remote and multi-machine agent deployments
  • Pairs cleanly with GitHub MCP for a complete issue-to-PR automation loop
  • Free to use with a standard Linear API key; no extra billing layer

Cons

  • API key permissions are workspace-wide by default — per-team scoping requires careful token discipline
  • Docs and roadmap surfaces have limited tool coverage compared to issues and projects
  • HTTP transport requires a running server process; stdio is simpler for local-only setups
  • No built-in rate-limit handling for high-volume agent loops

Key facts

What we have checked

Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.

Install

Add Linear MCP Server to your client

Not verified yet

No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.

Until then, follow the project's own README.

Works with

What Linear MCP Server connects to

1 product, each with how we know and when we checked.

Works withTypeHow we knowChecked
LinearProductIts homepage is on the product's own domainofficialLink on linear.applinear.app

Alternatives

Alternatives to Linear MCP Server

RecordTypeHow we knowChecked
Atlassian MCP ServerThis is an alternative to itMCP serverNamed in the listingNot dated
Notion MCP ServerThis is an alternative to itMCP serverNamed in the listingNot dated

Compare

Compare Linear MCP Server side by side

Sources

Where this comes from

No sources recorded yet. Each source we check is listed here with the date we checked it.

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.