archive-issue | Archives an existing Linear issue by its ID, removing it from active views while preserving its data for future reference. |
archive-project | Archives an existing Linear project by its UUID, removing it from active views. |
archive-project-update | Archives a project update in Linear, hiding it from the default view while preserving its data. |
create-attachment | Creates a new attachment and associates it with a specific, existing Linear issue. |
create-comment-reaction | Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue. |
create-comment | Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible - confirm the target issue and… |
create-issue | Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee… |
create-issue-relation | Create a relationship between two Linear issues using the issueRelationCreate mutation. |
create-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 | Tool to create a project milestone in Linear with a name and optional target date and sort order. |
create-project-update | Tool to create a project status update post for a Linear project. |
create-team | Creates a new team in Linear with the specified name and key. |
delete-issue | Archives an existing Linear issue by its ID, which is Linear’s standard way of deleting issues; the operation is idempotent. |
get-all-teams | DEPRECATED: Use ListLinearTeams instead (returns paginated payloads with members and projects); this tool returns simpler id/name-level data for all… |
get-attachment | Downloads a specific attachment from a Linear issue; the file_name must include the correct file extension. |
get-comment | Retrieves a single Linear comment by its unique ID. Returns comprehensive details including the comment body, author, timestamps, associated issue… |
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… |
get-cycles-by-team-id | Retrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints). |
get-issue-defaults | Fetches a Linear team’s default issue estimate and state, useful for pre-filling new issue forms. |
get-issue | Retrieves an existing Linear issue’s comprehensive details, including id, identifier, title, description, timestamps, state, team, creator… |
get-project | 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. |
get-project-update | Retrieves a specific project update by its unique identifier. |
list-comments | Lists comments from Linear workspace accessible to the authenticated user. |
list-issue-drafts | Tool to list issue drafts. Use when you need to fetch draft issues for review or further editing. |
list-issues-by-team-id | Tool to list all issues for a specific Linear team, scoped by team ID. |
list-cycles | Retrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied. |
list-issues | Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned. |
list-labels | Retrieves labels from Linear. If team_id is provided, returns labels for that specific team; if omitted, returns all labels across the workspace. |
list-projects | Retrieves all projects from the Linear account. Returns a flat array (not a GraphQL connection) with fields id and name; use… |
list-states | Retrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team’s workflow. |
list-teams | Retrieves all teams with their members and projects. Use stable team IDs or keys (not display names) for subsequent operations - names are non-unique. |
list-users | Lists all workspace users (not team-scoped) with their IDs, names, emails, and active status. |
list-project-updates | Retrieves all project updates from the Linear workspace. Project updates are status posts written by team members to communicate project progress, blockers, and health. |
remove-issue-label | Removes a specified label from an existing Linear issue using their IDs; successful even if the label isn’t on the issue. |
remove-reaction | Tool to remove a reaction on a comment. Use when you have a reaction ID and need to delete it. |
resolve-comment | Marks a Linear comment as resolved. This action is used when a comment thread or discussion has been addressed and should be marked as complete. |
run-query-or-mutation | Execute any GraphQL query or mutation against Linear’s API. USE WHEN: No dedicated action exists, need complex filtering, custom fields, or schema… |
search-issues | Search Linear issues using full-text search across identifier, title, and description. |
unarchive-project-update | Unarchive a previously archived project update in Linear. Use this action when you need to restore an archived project update to make it visible and active again. |
unresolve-comment | Unresolves a previously resolved Linear comment, marking it as requiring attention again. |
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… |
update-comment | 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. |
update-project | Tool to update an existing Linear project. Use when you need to modify project properties like name, description, state, dates, or lead. |
update-project-update | Tool to update an existing Linear project update post. Use this action when you need to modify a project update’s content, health status, or diff visibility settings. |
update-team | Updates an existing Linear team’s settings and configuration. |
validate-credential | Validates the Linear API credentials by checking if the authentication token can successfully query the current user. |