Linear

Create attachment (deprecated)

Deprecated fallback for tiny files only. Accepts base64 file content, verifies SHA-256 checksum, and uploads it through the MCP worker. Prefer `prepare_attachment_upload` plus direct PUT plus `create_attachment_from_upload`. CRITICAL: Do not print base64Content and then copy it into this tool call. Opaque base64 copied through model-visible text is easy to corrupt. Generate base64Content mechanically from the source bytes and pass it through a programmatic argument construction path whenever available. Before calling this tool, verify the values are consistent: Unix-like shells: file="/path/to/file" base64Content=$(base64 < "$file" | tr -d '\n\r') sha256=$(shasum -a 256 "$file" | awk '{print $1}') decodedSha256=$(printf '%s' "$base64Content" | base64 -d | shasum -a 256 | awk '{print $1}') size=$(wc -c < "$file" | tr -d ' ') # optional; stat can also get file byte size decodedSize=$(printf '%s' "$base64Content" | base64 -d | wc -c | tr -d ' ') PowerShell: $file = 'C:\path\to\file' $bytes = [IO.File]::ReadAllBytes($file) $base64Content = [Convert]::ToBase64String($bytes) $sha256 = (Get-FileHash -Algorithm SHA256 -Path $file).Hash.ToLower() $size = $bytes.Length # optional $decoded = [Convert]::FromBase64String($base64Content) $decodedStream = [IO.MemoryStream]::new($decoded) $decodedSha256 = (Get-FileHash -Algorithm SHA256 -InputStream $decodedStream).Hash.ToLower() $decodedSize = $decoded.Length decodedSha256 must equal sha256. If you pass size, decodedSize must equal size. Pass `sha256`. Passing `size` is optional, but recommended for clearer mismatch errors.

Requiredissuebase64ContentfilenamecontentTypesha256

Create attachment from upload

Link an already-uploaded Linear assetUrl to an existing issue as an attachment. Use this only after: 1. prepare_attachment_upload returned an assetUrl and uploadRequest. 2. The client successfully PUT raw file bytes to uploadRequest.url. This tool does not upload file content. It only creates the Linear attachment row. If the direct upload failed or the signed URL expired, rerun prepare_attachment_upload and upload again.

RequiredissueassetUrl

Create issue label

Create a new Linear issue label

Requiredname

Delete attachment

Delete an attachment by ID

Requiredid

Delete comment

Delete a Linear comment. Inline description comments (those with non-null `quotedText`) anchor a mark in the editor, so their root cannot be deleted — delete the replies individually or resolve the thread instead.

Requiredid

Delete diff comment

Delete a comment or persisted draft from a Linear diff

Delete status update

Delete (archive) a project or initiative status update.

Requiredtypeid

Extract images

Extract and fetch images from markdown content. Use this to view screenshots, diagrams, or other images embedded in Linear issues, comments, or documents. Pass the markdown content (e.g., issue description) and receive the images as viewable data.

Requiredmarkdown

Get agent skill

Retrieve a Linear Agent skill by ID, including its full markdown instructions.

Requiredid

Get attachment

Retrieve an attachment's content by ID.

Requiredid

Get diff

Exact lookup for a Linear diff. Use with review URLs, GitHub PR URLs, Linear full identifiers, UUIDs, or slugs.

RequiredurlOrId

Get diff threads

Exact lookup for diff threads and the authenticated user's drafts. Use with review URLs, GitHub PR URLs, Linear full identifiers, UUIDs, or slugs.

RequiredurlOrId

Get document

Retrieve a Linear document by ID or slug

Requiredid

Get issue

Retrieve detailed information about an issue by ID, including attachments, git branch name, and active Triage Intelligence suggestions when the issue is in triage

Requiredid

Get issue status

Retrieve detailed information about an issue status in Linear by name or ID

Requiredidnameteam

Get milestone

Retrieve details of a specific milestone by ID or name

Requiredprojectquery

Get project

Retrieve details of a specific project in Linear

Requiredquery

Get release

Retrieve details of a release by ID or slug.

Requiredid

Get release notes

Retrieve release notes by ID or slug, including markdown content.

Requiredid

Get status updates

List or get project/initiative status updates. Pass `id` to get a specific update, or filter to list.

Requiredtype

Get team

Retrieve details of a specific Linear team

Requiredquery

Get user

Retrieve details of a specific Linear user

Requiredquery

Get workspace

Retrieve the connected Linear workspace

List agent skills

List Linear Agent skills available to the authenticated user.

List comments

List comments on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. Provide exactly one of `issueId`, `projectId`, `initiativeId`, `documentId`, `milestoneId`, or `statusUpdateId`. For issues, projects, and initiatives this returns both top-level discussion threads and inline description comments. Inline (anchored) comments carry a non-null `quotedText` set to the snippet of description text they reference. Returned comments include `author` and nullable `onBehalfOf`; when set, `onBehalfOf` identifies the user the agent author acted for.

List cycles

Retrieve cycles for a specific Linear team

RequiredteamId

List diffs

List Linear diff pull requests visible to the authenticated user

List documents

List documents in the user's Linear workspace

List issue labels

List available issue labels in a Linear workspace or team

List issue statuses

List available issue statuses in a Linear team

Requiredteam

List issues

List issues in the user's Linear workspace, including active Triage Intelligence suggestions for issues in triage. For my issues, use "me" as the assignee. Use "null" for no assignee.

List project milestones

List all milestones in a Linear project

Requiredproject

List project labels

List available project labels in the Linear workspace

List projects

List projects in the user's Linear workspace

List release notes

List release notes in the workspace, optionally filtered by pipeline or covered release.

List release pipelines

List release pipelines in the workspace.

List releases

List releases in the workspace, with optional filtering by pipeline, stage, version, and text.

List teams

List teams in the user's Linear workspace

List users

Retrieve users in the Linear workspace

Merge diff

Merge a Linear diff or add it to the repository's merge queue

RequiredurlOrId

Prepare attachment upload

Prepare a direct Linear file upload for an existing issue. Workflow: 1. Call this tool with issue, filename, contentType, and size. 2. Upload raw bytes with PUT to uploadRequest.url outside MCP. 3. All headers in uploadRequest.headers are part of the signed request, so send them verbatim. 4. After PUT succeeds, call create_attachment_from_upload with assetUrl to link it to the issue. Do not base64-encode or transform the file. Use curl --data-binary @path or fetch(url, { method: 'PUT', body: blob }). Omitting or modifying any signed header, including casing, will return HTTP 403. The signed URL must be used within 60 seconds or it will expire. Upload sequencing: Prepare, PUT, and finalize one file before calling this tool for another file. Do not batch multiple prepare_attachment_upload calls before starting the PUTs because earlier signed URLs can expire while later files are prepared. Example: curl -X PUT --data-binary @file.png \ -H "content-type: image/png" \ -H "x-goog-content-length-range: N,N" \ -H "cache-control: public, max-age=31536000" \ -H 'Content-Disposition: attachment; filename="file.png"' \ "<uploadRequest.url>"

RequiredissuefilenamecontentTypesize

Resolve diff thread

Resolve or reopen a top-level comment thread on a Linear diff

RequiredthreadId

Save comment

Create or update a comment on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. If `id` is provided, updates the existing comment; otherwise creates a new one. To start a new thread, pass `body` and exactly one of `issueId`, `projectId`, `initiativeId`, `documentId`, `milestoneId`, or `statusUpdateId` — comments on issues/projects/initiatives become top-level discussion threads; comments on documents/milestones become description comments. A status update holds a single thread, so a comment on an update that already has one is added to it as a reply. To reply to an existing thread, pass `parentId` and `body`; the reply inherits the parent's thread type, so no entity reference is needed. Parent reference fields are ignored when `id` or `parentId` is provided (`statusUpdateType` is rejected instead).

Requiredbody

Save diff comment

Create, reply to, or edit a comment or persisted draft on a Linear diff. Set draft to true to save without submitting. Provide draftId to edit or submit a persisted draft, and commentId only to edit a submitted comment. Submitting an inline draft reuses its saved anchor; submitting a reply draft requires parentId again.

Requiredbody

Save document

Create or update a Linear document. If `id` is provided, updates the existing document; otherwise creates a new one. When creating, `title` is required and exactly one parent (`project`, `issue`, `initiative`, `cycle`, or `team`) must be specified. On update, passing a parent reparents the document. To change parts of the content without resending all of it, pass `patch` instead of `content`.

Save issue

Create or update a Linear issue. If `id` is provided, updates the existing issue; otherwise creates a new one. When creating, `title` and `team` are required. Note: use `assignee` (not `assigneeId`) to set the assignee — it accepts a user ID, name, email, or "me".

Save milestone

Create or update a milestone in a Linear project. If `id` is provided, updates the existing milestone; otherwise creates a new one. When creating, `name` is required.

Requiredproject

Save project

Create or update a Linear project. If `id` is provided, updates the existing project; otherwise creates a new one. When creating, `name` and at least one team (via `addTeams` or `setTeams`) are required. To change parts of the description without resending all of it, pass `patch` instead of `description`.

Save release

Create or update a release. If `id` is provided, updates the existing release; otherwise creates a new one. When creating, `name` and `pipeline` are required. Release status is modeled as the release pipeline stage.

Save release notes

Create or update release notes. If `id` is provided, updates the existing release notes; otherwise creates a new one. When creating, `pipeline` and either `releases` or a release range are required. To change parts of the content without resending all of it, pass `patch` instead of `content`.

Save status update

Create or update a project/initiative status update. Omit `id` to create, provide `id` to update.

Requiredtype

Search documentation

Search Linear's documentation to learn about features and usage

Requiredquery

Submit diff review

Approve a Linear diff, request changes, or submit a review comment

RequiredurlOrIddecision