# Linear MCP

> Linear MCP connects your agent directly to your issue tracking workspace. List all tickets, get detailed metadata on any bug or feature request, and update status across projects using natural conversation. It lets you coordinate agile development cycles without ever leaving your chat window.

## Overview
- **Category:** loved-by-devs
- **Price:** Free
- **Tags:** issue-tracking, agile, sprint-planning, workflow-automation, task-management, software-delivery

## Description

Need to know the state of a project? This MCP gives your AI agent full control over your Linear workspace. Instead of jumping through multiple tabs to gather info on bugs or features, you talk to your agent. You can list all active tickets and pull detailed metadata instantly. Want to update status for a whole team? Your agent handles it. It's like having a dedicated project coordinator that lives inside your chat app. When you connect this MCP via Vinkius, your AI client becomes an agile architect for your entire organization. You manage everything from creating brand new issues to adding contextual comments and verifying the health of your API connection, all in plain conversation.

## Tools

### create_linear_comment
Adds a comment directly to any specific issue ticket for team context.

### create_linear_issue
Creates an entirely new issue within the Linear workspace.

### get_linear_issue
Retrieves comprehensive, detailed information about one specific ticket.

### list_linear_cycles
Lists all active development cycles currently running in your organization.

### list_linear_issues
Provides a broad list of issues across the workspace, showing their general status.

### list_linear_labels
Retrieves a directory of all issue labels used by your teams.

### list_linear_projects
Lists and shows the status of all active projects within Linear.

### list_linear_teams
Lists all distinct teams or departments that belong to your workspace.

### list_linear_users
Retrieves a directory listing of all individual members in the Linear workspace.

### check_linear_status
Runs a check to confirm that your API connection is active and working correctly.

### update_linear_issue
Changes the status or details of an existing ticket using natural language instructions.

## Prompt Examples

**Prompt:** 
```
List all active issues and show their status.
```

**Response:** 
```
I've retrieved your issues. You currently have 15 active high-fidelity tickets, including 'API Integration' (In Progress) and 'UI Bug' (Backlog). Would you like to see the detailed metadata for any of them?
```

**Prompt:** 
```
Create a new issue for the 'Frontend' team titled 'Implement Dashboard'.
```

**Response:** 
```
Issue orchestrated! I've successfully created 'Implement Dashboard' (ID: FRONT-45) for the Frontend team. This high-fidelity update is now live in Linear. Shall I verify the team's current technical velocity?
```

**Prompt:** 
```
Check the team members in the 'Mobile' team.
```

**Response:** 
```
Team directory orchestrated! The 'Mobile' team currently has 8 high-fidelity profiles assigned. Your API connection is healthy. Shall I retrieve the detailed resource utilization metadata for this team?
```

## Capabilities

### Track project progress
List active projects, cycles, labels, and teams to understand your organizational structure.

### View issue details
Retrieve full metadata for a specific ticket, including its current status and history.

### Manage tickets
Create new issues or update the status of existing ones programmatically.

### Communicate contextually
Add specific comments to an issue, ensuring team members see the latest updates right where they belong.

### Check workspace health
Verify that your API connection is working correctly and check overall service status.

## Use Cases

### Need a status report on three different features?
A Product Manager needs to know the current state of 'Dashboard UI', 'Auth Fix', and 'Billing Flow' before a stakeholder meeting. They ask their agent, and it executes get_linear_issue for all three tickets, compiling the detailed metadata into a single conversational summary.

### A team needs a new bug ticket created immediately.
An Engineer finds a critical issue during testing. Instead of navigating to 'Create Issue,' they simply ask their agent to create_linear_issue with the title and description, ensuring it gets assigned to the right project.

### The team structure changed, who owns this feature?
A DevOps Lead needs to know which department is responsible for a legacy system. They ask their agent to list_linear_teams and then use list_linear_users to pinpoint the right owner.

### Need to update tickets after a sprint planning meeting.
The PM asks the agent to update_linear_issue for all high-priority bugs from the previous cycle, changing their status from 'Backlog' to 'Ready for Dev,' confirming everything in one go.

## Benefits

- Stop manually updating statuses. You can tell your agent to update an existing issue or create a new one instantly, keeping all development records current without opening the app.
- Get instant team directory insight. List workspace teams and members to understand exactly who is assigned what, saving time when coordinating cross-functional efforts.
- Understand project scope quickly. By listing active projects or cycles, you get a clear overview of which goals are currently being worked on across different departments.
- Maintain perfect context. Instead of emailing updates, use the MCP to add specific comments directly to an issue, keeping all historical notes tied to the ticket itself.
- Coordinate complex tasks. Your agent can pull detailed information for any single issue and then allow you to update it in one go, dramatically reducing clicks.

## How It Works

The bottom line is you talk to your agent once; it does the manual work inside Linear and gives you the answer back.

1. First, subscribe to this MCP in Vinkius. Then, grab your Personal API Key from the Linear settings page.
2. Connect that key to your preferred AI client (like Cursor or Claude).
3. Ask your agent a question like, 'List all active issues for the Frontend team,' and it executes the command.

## Frequently Asked Questions

**Can I use Linear MCP to list all projects?**
Yes, you can. Use the MCP's tools to run list_linear_projects. This gives your agent a directory of every active project in your workspace so you know where everything is.

**How do I update an issue status using Linear MCP?**
You use the update_linear_issue tool. You simply ask your agent to change the status for a specific ticket, and it handles updating the record in Linear automatically.

**Does Linear MCP help me track team members?**
Absolutely. The list_linear_users tool lets you retrieve a directory of all workspace members. This is critical when figuring out who owns which feature or bug.

**What if I need to add context to an issue? Is it Linear MCP?**
Yes, use the create_linear_comment tool. You can have your agent write and post a comment to any specific issue, keeping perfect communication history right where the work happens.

**Is Linear MCP just for reading data from my issues?**
No, it's fully bi-directional. Beyond listing or getting details, you can also create_linear_issue and update existing ones, making your agent an active participant in the workflow.