Linear

Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue.

Creates a new attachment and associates it with a specific, existing Linear issue.

Creates a new comment on a specified Linear issue.

Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing for optional properties like description, assignee, state, priority, cycle, and due date.

Fetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.

Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned.

Creates a new Linear project with specified name and team associations.

Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent.

Retrieves all teams from the Linear workspace without requiring any parameters.

Downloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension.

Gets the currently authenticated user's ID, name, email, and other profile information. Use this to identify 'me' in other Linear operations that require user ID filtering.

Retrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints) and the team ID must correspond to an existing team.

Retrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments, and due date.

Retrieves a single Linear project by its unique identifier. Use when verifying a newly created or updated project, or when fetching detailed project information by ID.

Tool to list issue drafts. Use when you need to fetch draft issues for review or further editing.

Tool to list all issues for a specific Linear team, scoped by team ID. Use when you need to retrieve issues belonging to a particular team without fetching workspace-wide issues. This is more efficient than workspace-wide listing followed by client-side filtering.

Retrieves all cycles (time-boxed iterations for work) from the Linear account; no filters are applied.

Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned. Can also filter by assignee_id to get issues assigned to a specific user.

Retrieves labels from Linear. If team_id is provided, returns labels for that specific team. If team_id is omitted, returns all labels across the workspace.

Retrieves all projects from the Linear account.

Retrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team's workflow.

Retrieves all teams with their members. Optionally filters each team's associated projects by project_id.

Lists all users in the Linear workspace with their IDs, names, emails, and active status.

Tool to create, update, or delete issue drafts in Linear. Use when you need to save or modify draft notes before converting to an issue. Note: Linear's public GraphQL API does not expose explicit Issue Draft mutations. This action leverages standard Issue mutations to emulate draft management: - create -> issueCreate - update -> issueUpdate - delete -> issueDelete The response maps the created/updated Issue fields to the DraftModel for compatibility.

Removes a specified label from an existing Linear issue using their IDs; successful even if the label isn't on the issue.

Tool to remove a reaction on a comment. Use when you have a reaction ID and need to delete it.

Execute any GraphQL query or mutation against Linear's API. USE WHEN: No dedicated action exists, need complex filtering, custom fields, or schema discovery. *** INTROSPECTION FIRST - NEVER GUESS FIELD NAMES *** Run introspection before unknown operations: - query { __type(name: "Issue") { fields { name } } } - query { __type(name: "Mutation") { fields { name } } } Linear uses nested objects (project { id }), NOT scalar IDs (projectId). KEY: All IDs are UUIDs. Filter: { field: { eq: value } }. Pagination: nodes[] + pageInfo.

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.

Tool to update an existing Linear comment's body text. Use when you need to edit or modify the content of a previously created comment.

Tool to update an existing Linear project. Use when you need to modify project properties like name, description, state, dates, or lead. All fields except project_id are optional - only provide the fields you want to update.