Linear MCP Server

Linear MCP Server
Connect Claude to Linear through Linear's hosted remote MCP server.

Linear MCP Server

Connect Claude to Linear through Linear's hosted remote MCP server.

The Linear MCP Server enables Claude to read issues, create tasks, update project status, and interact with your engineering workflow using natural language commands.

What Can Claude Do with the Linear MCP Server?

The Linear MCP Server exposes Linear API functionality to Claude through the Model Context Protocol.

Core capabilities:

  • Read Issues — View issue details, status, assignees, and project information
  • Create Tasks — Add new issues with titles, descriptions, labels, and priorities
  • Update Issues — Modify issue status, assignees, estimates, and other properties
  • Search Projects — Find issues by project, team, status, or label
  • Team Management — Access team information and member assignments

Access scope: Claude can only access Linear data based on your OAuth authorization. The integration respects Linear workspace permissions and team access settings.

How to Install the Linear MCP Server

Linear provides a hosted remote MCP server.

For Claude Code and Other MCP Clients

Connect to the remote Linear MCP endpoint using your MCP client's OAuth connection flow.

Endpoint reference: https://mcp.linear.app/mcp

Authentication uses OAuth 2.1 with dynamic client registration. You'll be redirected to authorize access during setup.

OAuth Authorization

The Linear MCP Server uses OAuth for secure authentication:

  1. Your MCP client initiates connection to Linear's hosted MCP server
  2. You're redirected to Linear's authorization page
  3. You authorize the requested workspace and team access
  4. Linear generates access credentials
  5. Your MCP client stores these credentials securely

Linear MCP Use Cases & Project Management Examples

Example workflows that become possible with the Linear MCP Server.

View Issue Details

Example prompt:

> "Show me the details of issue ENG-123."

Claude can retrieve issue information including title, description, status, and assignee.

Create New Tasks

Example prompt:

> "Create a new issue in the Engineering team titled 'Fix login bug' with priority High and label 'bug'."

Claude can create issues with specified properties.

Update Issue Status

Example prompt:

> "Move issue ENG-456 to In Progress and assign it to me."

Claude can update issue status and assignments.

Search by Criteria

Example prompt:

> "Find all high-priority bugs in the current cycle that are unassigned."

Claude can search issues based on multiple filters.

List Team Backlog

Example prompt:

> "Show me all issues in the Engineering team backlog ordered by priority."

Claude can query and organize team issues.

Track Sprint Progress

Example prompt:

> "How many issues are completed in the current cycle for the Backend team?"

Claude can aggregate issue data by cycle or project.

Note: These are example use cases. Actual capabilities depend on your OAuth permissions, team access, and the MCP server's current feature set.

Linear MCP in a Product Delivery Loop

Linear MCP is a real fit for product-engineering teams that want issue creation, updates, and planning directly from assistant conversations.

What this shows: This screenshot shows Linear's MCP documentation, reflecting the day-to-day scenario of tying AI assistance to issue tracking and delivery workflows.

Why this scenario matters: It shows the real issue-tracking surface where assistant actions create value, especially when product and engineering teams move directly from discussion into execution.

Typical assistant task: Create issues, update delivery state, and move from discussion into execution inside one planning system.

Source: Linear MCP Docs

When to Pick Linear MCP Server vs Jira Cloud API

This comparison is most useful when both options look plausible on paper but differ in operating model, team fit, and day-to-day workflow cost.

Decision LensThis Page's MCP PathCompetitor
Best ForFast-moving product and engineering teams that want tight issue loops and lightweight planning.Organizations with heavier process requirements, larger workflow footprints, or legacy issue operations.
Where MCP WinsLinear MCP wins when speed, clarity, and low-friction issue handling matter more than process depth.
Tradeoff to WatchIt is not the best fit when the team depends on Jira-grade workflow complexity and enterprise process compatibility.
Choose This Path WhenChoose Linear MCP for lean delivery loops; choose the Jira API when enterprise workflow depth matters more.
Sources

Frequently Asked Questions

Is the Linear MCP Server free?
The MCP Server itself is provided by Linear. Linear offers free plans for small teams and paid plans for larger organizations. The API is available on all plans.
Do I need to create an API key?
No. The primary modern connection path uses Linear's hosted remote MCP with OAuth. API key-based approaches may exist in older or custom integrations.
Can Claude access all teams in my workspace?
Access depends on your Linear account permissions and what you authorize during OAuth. You control which teams Claude can access.
Does it work with Linear cycles (sprints)?
Yes. Claude can query issues by cycle, view cycle progress, and access cycle-related information through the Linear API.
Can Claude create projects or teams?
Project and team creation depends on your OAuth permissions and the MCP server's exposed tools. Most implementations focus on issue management.
How do I revoke access?
Go to Linear Settings → API → OAuth Applications → find the authorized MCP connection → Revoke access.
Does it work with Linear's GraphQL API?
Yes. Linear's API uses GraphQL. The MCP Server wraps this API to expose functionality through the Model Context Protocol.

Use Linear MCP in Verdent

Verdent provides streamlined Linear integration. This is Verdent's platform-level integration flow, not the default setup path from Linear's official documentation.

Connect your Linear workspace once and access project management operations across all Verdent projects without repeated authorization flows.

Connect Linear in Verdent