Linear MCP integration
Searches issues, files new ones with attachments, updates state, labels, and assignees, and maintains projects and milestones.
32actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Create linear issue
Lyro creates a new issue in a Linear team's project, filling in the title and any other details available. A bug or request becomes a tracked ticket instead of a message lost in chat.
Get linear issue
Lyro retrieves a Linear issue's full details, including its state, assignee, and comments. Whoever's asking gets an instant status update without opening Linear.
Update issue
Lyro updates an existing Linear issue's state, assignee, or other fields on request. A ticket stays current without an engineer stopping to update it manually.
How businesses use Linear + Lyro
Each card is one request a support team gets, and the Linear actions Lyro runs to close it.
Check whether the bug is already known
Lyro searches Linear for an existing issue matching the report, reads the one it finds, and checks what the team is carrying in the current cycle, so a duplicate is not filed.
Search Linear IssuesGet Linear IssueList Issues By Team IdFile the issue with the conversation attached
Lyro creates the issue in the reporter's own words, attaches the conversation or file behind it, and adds the comment that gives an engineer the context they need to start.
Create Linear IssueCreate AttachmentCreate A CommentKeep an issue's state honest as it moves
Lyro moves an issue into the right state, adjusts its labels, and links it to the issue it blocks or duplicates, so the board reflects what is actually happening.
Update IssueRemove Label From Linear IssueCreate Issue RelationKeep a project readable to everyone watching
Lyro sets up the project and the milestone it is working toward, and posts the project update that tells stakeholders where things stand without anyone chasing.
Create ProjectCreate Project MilestoneCreate Project Update
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Linear actions it has and picks the ones a request needs.
- 01
Connect Linear
Authorize the Linear account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
- 02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Linear actions that close it and chains as many as the request needs.
- 03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free
Everything else about Linear
Setup, permissions, and the limits of what Lyro can do inside Linear.
It reads them first. Get Create Issue Default Params returns the defaults for creating an issue, List Linear States returns the workflow states that team actually uses, and Get Labels and Get Teams cover the rest, so an issue is created valid instead of landing in a state nobody triages.
Every action available in Linear
All 32 actions your agent can call on Linear, straight from the live MCP connection.
Create attachment
Creates a new attachment and associates it with a specific, existing Linear issue.
Add reaction to comment
Add a reaction to an existing Linear comment.
Create a comment
Creates a new comment on a specified Linear issue.
Create linear issue
Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date.
Create issue relation
Create a relationship between two Linear issues using the issueRelationCreate mutation.
Create a label
Creates a new label in Linear for a specified team, used to categorize and organize issues.
Create project
Creates a new Linear project with specified name and team associations.
Create project milestone
Create a project milestone in Linear with a name and optional target date and sort order.
Create project update
Create a project status update post for a Linear project.
Delete issue
Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent.
Download issue attachments
Downloads a specific attachment from a Linear issue; the file_name must include the correct file extension.
Get current user
Gets the currently authenticated user's ID, name, email, and other profile information — this is the account behind the API token, which may be a bot or service account rather than a human user.
Get cycles by team ID
Retrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints).
Get create issue default params
Fetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.
Get linear issue
Retrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use issue.comments.nodes for comment IDs), subscribers, and due date.
Get linear project
Retrieves a single Linear project by its unique identifier.
List issue drafts
List issue drafts.
List issues by team ID
List all issues for a specific Linear team, scoped by team ID.
Get all cycles
Retrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied.
List linear issues
Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned.
Get labels
Retrieves labels from Linear.
List linear projects
Retrieves all projects from the Linear account.
List linear states
Retrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team's workflow.
Get teams
Retrieves all teams with their members and projects.
List linear users
Lists all workspace users (not team-scoped) with their IDs, names, emails, and active status.
Remove label from linear issue
Removes a specified label from an existing Linear issue using their IDs; successful even if the label isn't on the issue.
Remove reaction from comment
Remove a reaction on a comment.
Run query or mutation
Execute any GraphQL query or mutation against Linear's API.
Search linear issues
Search Linear issues using full-text search across identifier, title, and description.
Update issue
Updates an existing Linear issue using its issue_id; requires at least one other attribute for modification, and all provided entity IDs (for state, assignee, labels, etc.) must be valid UUIDs — only issueId accepts key format (e.g., 'ENG-123').
The tools Linear sits next to
Same connection, same setup. Pick the next one your team already uses.
Agiled
Opens tickets, creates projects and tasks, logs expenses, and reads the invoices, estimates, and timesheets behind a client question.
Desktime
Starts and stops time tracking, reports an employee's hours and active project, and creates new projects from the conversation.
Harvest
Logs hours to the right project, sends estimates from a scoping conversation, raises invoices and records payments, and sets new clients up to bill.
Moco
Logs time against the right project, reports budget and utilisation, raises and emails invoices from tracked hours, and chases what has gone unpaid.
Rize
Register cardholders and users, issue cards and pull the virtual card image, provision financial accounts and counterparties, and mint API keys.
Timecamp
Pulls the account's project list with assigned users, budgets, dates, and archived status, so project questions are answered from live data.
Ready to connect Linear?
Authorize the account and your agent has all 32 actions from the first conversation.