Linear

Fetch a Linear issue, project, initiative, or document by entity-prefixed ID. Use to get full details for results returned by the search tool. Also works with any known identifier.

fetch

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

get_agent_skill

Retrieve an attachment's content by ID.

get_attachment

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

get_diff

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

get_diff_threads

Retrieve a Linear document by ID or slug

get_document

Retrieve detailed information about a specific initiative in Linear

get_initiative

Retrieve detailed information about an issue by ID, including attachments and git branch name

get_issue

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

get_issue_status

Retrieve details of a specific milestone by ID or name

get_milestone

Retrieve the profile of the currently authenticated user

get_profile

Retrieve details of a specific project in Linear

get_project

Retrieve details of a release by ID or slug.

get_release

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

get_release_note

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

get_status_updates

Retrieve details of a specific Linear team

get_team

Retrieve details of a specific Linear user

get_user

List Linear Agent skills available to the authenticated user.

list_agent_skills

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.

list_comments

List customers in the user's Linear workspace

list_customers

Retrieve cycles for a specific Linear team

list_cycles

List Linear diff pull requests visible to the authenticated user

list_diffs

List documents in the user's Linear workspace

list_documents

List available initiative labels in the Linear workspace

list_initiative_labels

List initiatives in the user's Linear workspace

list_initiatives

List available issue labels in a Linear workspace or team

list_issue_labels

List available issue statuses in a Linear team

list_issue_statuses

List issues in the user's Linear workspace. For my issues, use "me" as the assignee. Use "null" for no assignee.

list_issues

List available project labels in the Linear workspace

list_project_labels

List all milestones in a Linear project

list_milestones

List projects in the user's Linear workspace

list_projects

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

list_release_notes

List release pipelines in the workspace.

list_release_pipelines

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

list_releases

List teams in the user's Linear workspace

list_teams

Retrieve users in the Linear workspace

list_users

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>"

prepare_attachment_upload

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).

save_comment

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

save_customer

Create or update a customer need (request) in Linear. If `id` is provided, updates the existing need; otherwise creates a new one. When creating, `body` is required.

save_customer_need