Skip to Content
ResourcesIntegrationsProductivity & DocsLinear

Linear

Service domainPROJECT MANAGEMENT
Linear icon
Arcade Optimized

Arcade tools designed for LLMs to interact with Linear

Author:Arcade
Version:4.0.0
Auth:User authorization via the Linear auth provider
46tools

Linear Toolkit

The Linear toolkit connects LLMs to Linear via Arcade, enabling programmatic management of issues, projects, initiatives, cycles, comments, and workspace structure.

Capabilities

  • Issue lifecycle: Create, update, archive, transition workflow states, manage relations (blocks/blocked-by/duplicate/related), link GitHub PRs/commits, subscribe to notifications, and retrieve detailed issue data with fuzzy-matched entity resolution.
  • Projects & milestones: Create, update, archive, and list projects with status/team filters; upsert milestones; post and list project status updates; manage project statuses (including custom ones) workspace-wide.
  • Initiatives: Create, update, archive, and list strategic initiatives; link projects to initiatives; retrieve full paginated descriptions.
  • Comments & threads: Add, update, resolve/reopen, and reply to threaded comments on issues and project documents; list comments with filtering (quoted/unquoted/all); note that API-created project comments appear in the comments panel only — not visually anchored inline.
  • Workspace & teams: List teams, workflow states, labels, cycles, and available project statuses; look up specific teams, cycles, and milestones by ID or fuzzy name.
  • User context: Retrieve the authenticated user's profile, team memberships, notifications, and recent issue activity.

OAuth

This toolkit uses OAuth 2.0 via the Linear provider. See the Linear auth provider docs for setup details.

Available tools(46)

46 of 46 tools
Operations
Behavior
Tool nameDescriptionSecrets
Add a comment to an issue.
Add a comment to a project's document content. IMPORTANT: Due to Linear API limitations, comments created via the API will NOT appear visually anchored inline in the document (no yellow highlight on text). The comment will be stored and can be retrieved via list_project_comments, but it will appear in the comments panel rather than inline in the document. For true inline comments that are visually anchored to text, users should create them directly in the Linear UI by selecting text and adding a comment. The quoted_text parameter stores metadata about what text the comment references, which is useful for context even though the comment won't be visually anchored.
Link a project to an initiative. Both initiative and project can be specified by ID or name. If a name is provided, fuzzy matching is used to resolve it.
Archive an initiative. Archived initiatives are hidden from default views but can be restored.
Archive an issue. Archived issues are hidden from default views but can be restored.
Archive a project. Archived projects are hidden from default views but can be restored.
Create a new Linear initiative. Initiatives are high-level strategic goals that group related projects.
Create a new Linear issue with validation. When assignee is None or '@me', the issue is assigned to the authenticated user. All entity references (team, assignee, labels, state, project, cycle, parent) are validated before creation. If an entity is not found, suggestions are returned to help correct the input.
Create a relation between two issues. Relation types define the relationship from the source issue's perspective: - blocks: Source issue blocks the related issue - blockedBy: Source issue is blocked by the related issue - duplicate: Source issue is a duplicate of the related issue - related: Issues are related (bidirectional)
Create a new Linear project. Team is validated before creation. If team is not found, suggestions are returned to help correct the input. Lead is validated if provided.
Create a new project status in the Linear workspace. Requires Linear workspace admin access; without it the create fails. Status names are unique per category: the same name may exist once per type. When a status with the same name and type already exists, this returns a retryable error carrying the existing status's id so it can be reused instead of duplicated. A same-named status of a different type is allowed.
Create a project status update. Project updates are posts that communicate progress, blockers, or status changes to stakeholders. They appear in the project's Updates tab and can include a health status indicator.
Get detailed information about a specific Linear cycle.
Get detailed information about a specific Linear initiative. Supports lookup by ID or name (with fuzzy matching for name).
Get an initiative's full description with pagination support. Use this tool when you need the complete description of an initiative that was truncated in the get_initiative response. Supports chunked reading for very large descriptions.
Get detailed information about a specific Linear issue. Accepts either the issue UUID or the human-readable identifier (like TOO-123).
Get a milestone by ID or name inside a project.
Get the authenticated user's notifications. Returns notifications including issue mentions, comments, assignments, and state changes.
Get detailed information about a specific Linear project. Supports lookup by ID, slug_id, or name (with fuzzy matching for name).
Get a project's full description with pagination support. Use this tool when you need the complete description of a project that was truncated in the get_project response. Supports chunked reading for very large descriptions.
Get the authenticated user's recent issue activity. Returns issues the user has recently created or been assigned to within the specified time period.
Get detailed information about a specific Linear team. Supports lookup by ID, key (like TOO, ENG), or name (with fuzzy matching).
Link a GitHub PR, commit, or issue to a Linear issue. Automatically detects the artifact type from the URL and generates an appropriate title if not provided.
List the project statuses a project can be put in, in the Linear workspace. Includes custom statuses, not just the built-in categories, so the exact name, id, and type of each status can be discovered before filtering projects by status or assigning a status to a project. Returned in lifecycle order (backlog → planned → started → paused → completed → canceled), then by position within each category. Project statuses are a small workspace-level vocabulary and the whole set is returned in one call (no pagination).
List comments on an issue. Returns comments with user info, timestamps, and reply threading info.
Page 1 of 2(25 of 46)
Last updated on