Automate Linear without writing code.

• Archive issueArchives an existing Linear issue by its ID, removing it from active views while preserving its data for future reference. Use this action w
• Archive projectArchives an existing Linear project by its UUID, removing it from active views. Use this action when you need to mark a completed or obsolet
• Archive project updateArchives a project update in Linear, hiding it from the default view while preserving its data. Use this action when you need to clean up ol
• Create attachmentCreates a new attachment and associates it with a specific, existing Linear issue.
• Create comment reactionTool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue.
• Create linear commentCreates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target iss
• Create linear issueCreates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description,
• Create linear issue relationCreate a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'du
• Create linear labelCreates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If
• Create linear projectCreates a new Linear project with specified name and team associations.
• Create project milestoneTool to create a project milestone in Linear with a name and optional target date and sort order. Use when you need to add milestones to tra
• Create project updateTool to create a project status update post for a Linear project. Use when you need to post progress updates, status reports, or announcemen
• Create teamCreates a new team in Linear with the specified name and key. Use this action when you need to create a new organizational unit or work grou
• Delete linear issueArchives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent. Archiving is pe
• Get all linear teamsDEPRECATED: Use ListLinearTeams instead (returns paginated payloads with members and projects); this tool returns simpler id/name-level data
• Get attachmentDownloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension.
• Get commentRetrieves a single Linear comment by its unique ID. Returns comprehensive details including the comment body, author, timestamps, associated
• Get current userGets the currently authenticated user's ID, name, email, and other profile information — this is the account behind the API token, which may
• Get cycles by team idRetrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints). Results are team-scoped to the given
• Get issue defaultsFetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.
• Get linear issueRetrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator,
• Get linear projectRetrieves a single Linear project by its unique identifier. Use when verifying a newly created or updated project, or when fetching detailed
• Get project updateRetrieves a specific project update by its unique identifier. Use when you need to fetch details about a specific project status update, inc
• List commentsLists comments from Linear workspace accessible to the authenticated user. Use this action when you need to retrieve comments for analysis,

+ 23 more