linear

Server Details

MCP server for Linear project management and issue tracking

Status: Healthy
Last Tested: 2026-03-20 22:30
Transport: Streamable HTTP
URL

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

31 tools

create_attachmentInspect

Create a new attachment on a specific Linear issue by uploading base64-encoded content.

ParametersJSON Schema

Name	Required	Description
`issue`	Yes	Issue ID or identifier (e.g., LIN-123)
`title`	No	Optional title for the attachment
`filename`	Yes	Filename for the upload (e.g., 'screenshot.png')
`subtitle`	No	Optional subtitle for the attachment
`contentType`	Yes	MIME type for the upload (e.g., 'image/png', 'application/pdf')
`base64Content`	Yes	Base64-encoded file content to upload

create_documentInspect

Create a new document in Linear

ParametersJSON Schema

Name	Required	Description
`icon`	No	Icon emoji
`color`	No	Hex color
`issue`	No	Issue ID or identifier (e.g., LIN-123)
`title`	Yes	Document title
`content`	No	Content as Markdown
`project`	No	Project name, ID, or slug

create_issue_labelInspect

Create a new Linear issue label

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Label name
`color`	No	Hex color code
`parent`	No	Parent label group name
`teamId`	No	Team UUID (omit for workspace label)
`isGroup`	No	Is label group (not directly applicable)
`description`	No	Label description

delete_attachmentInspect

Delete an attachment by ID

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Attachment ID

delete_commentInspect

Delete a comment from a Linear issue

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Comment ID

extract_imagesInspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`markdown`	Yes	Markdown content containing image references (e.g., issue description, comment body)

get_attachmentInspect

Retrieve an attachment's content by ID.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Attachment ID

get_documentInspect

Retrieve a Linear document by ID or slug

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Document ID or slug

get_issueInspect

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

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Issue ID or identifier (e.g., LIN-123)
`includeRelations`	No	Include blocking/related/duplicate relations
`includeCustomerNeeds`	No	Include associated customer needs

get_issue_statusInspect

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

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Status ID
`name`	Yes	Status name
`team`	Yes	Team name or ID

get_milestoneInspect

Retrieve details of a specific milestone by ID or name

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Milestone name or ID
`project`	Yes	Project name, ID, or slug

get_projectInspect

Retrieve details of a specific project in Linear

ParametersJSON Schema

Name	Required	Description
`query`	Yes	Project name, ID, or slug
`includeMembers`	No	Include project members
`includeResources`	No	Include resources (documents, links, attachments)
`includeMilestones`	No	Include milestones

get_teamInspect

Retrieve details of a specific Linear team

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Team UUID, key, or name

get_userInspect

Retrieve details of a specific Linear user

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	User ID, name, email, or "me"

list_commentsInspect

List comments for a specific Linear issue

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Max results (default 50, max 250)
`cursor`	No	Next page cursor
`issueId`	Yes	Issue ID or identifier (e.g., LIN-123)
`orderBy`	No	Sort: createdAt \| updatedAt	updatedAt

list_cyclesInspect

Retrieve cycles for a specific Linear team

ParametersJSON Schema

Name	Required	Description	Default
`type`	No	Filter: current, previous, next, or all
`teamId`	Yes	Team ID

list_documentsInspect

List documents in the user's Linear workspace

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Max results (default 50, max 250)
`query`	No	Search query
`cursor`	No	Next page cursor
`orderBy`	No	Sort: createdAt \| updatedAt	updatedAt
`createdAt`	No	Created after: ISO-8601 date/duration (e.g., -P1D)
`creatorId`	No	Filter by creator ID
`projectId`	No	Filter by project ID
`updatedAt`	No	Updated after: ISO-8601 date/duration (e.g., -P1D)
`initiativeId`	No	Filter by initiative ID
`includeArchived`	No	Include archived items

list_issue_labelsInspect

List available issue labels in a Linear workspace or team

ParametersJSON Schema

Name	Required	Description	Default
`name`	No	Filter by name
`team`	No	Team name or ID
`limit`	No	Max results (default 50, max 250)
`cursor`	No	Next page cursor
`orderBy`	No	Sort: createdAt \| updatedAt	updatedAt

list_issuesInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`team`	No	Team name or ID
`cycle`	No	Cycle name, number, or ID
`label`	No	Label name or ID
`limit`	No	Max results (default 50, max 250)
`query`	No	Search issue title or description
`state`	No	State type, name, or ID
`cursor`	No	Next page cursor
`orderBy`	No	Sort: createdAt \| updatedAt	updatedAt
`project`	No	Project name, ID, or slug
`assignee`	No	User ID, name, email, or "me"
`delegate`	No	Agent name or ID
`parentId`	No	Parent issue ID or identifier (e.g., LIN-123)
`priority`	No	0=None, 1=Urgent, 2=High, 3=Normal, 4=Low
`createdAt`	No	Created after: ISO-8601 date/duration (e.g., -P1D)
`updatedAt`	No	Updated after: ISO-8601 date/duration (e.g., -P1D)
`includeArchived`	No	Include archived items

list_issue_statusesInspect

List available issue statuses in a Linear team

ParametersJSON Schema

Name	Required	Description	Default
`team`	Yes	Team name or ID

list_milestonesInspect

List all milestones in a Linear project

ParametersJSON Schema

Name	Required	Description	Default
`project`	Yes	Project name, ID, or slug

list_project_labelsInspect

List available project labels in the Linear workspace

ParametersJSON Schema

Name	Required	Description	Default
`name`	No	Filter by name
`limit`	No	Max results (default 50, max 250)
`cursor`	No	Next page cursor
`orderBy`	No	Sort: createdAt \| updatedAt	updatedAt

list_projectsInspect

List projects in the user's Linear workspace

ParametersJSON Schema

Name	Required	Description	Default
`team`	No	Team name or ID
`label`	No	Label name or ID
`limit`	No	Max results (default 50, max 250)
`query`	No	Search project name
`state`	No	State type, name, or ID
`cursor`	No	Next page cursor
`member`	No	User ID, name, email, or "me"
`orderBy`	No	Sort: createdAt \| updatedAt	updatedAt
`createdAt`	No	Created after: ISO-8601 date/duration (e.g., -P1D)
`updatedAt`	No	Updated after: ISO-8601 date/duration (e.g., -P1D)
`initiative`	No	Initiative name or ID
`includeMembers`	No	Include project members
`includeArchived`	No	Include archived items
`includeMilestones`	No	Include milestones

list_teamsInspect

List teams in the user's Linear workspace

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Max results (default 50, max 250)
`query`	No	Search query
`cursor`	No	Next page cursor
`orderBy`	No	Sort: createdAt \| updatedAt	updatedAt
`createdAt`	No	Created after: ISO-8601 date/duration (e.g., -P1D)
`updatedAt`	No	Updated after: ISO-8601 date/duration (e.g., -P1D)
`includeArchived`	No	Include archived items

list_usersInspect

Retrieve users in the Linear workspace

ParametersJSON Schema

Name	Required	Description	Default
`team`	No	Team name or ID
`limit`	No	Max results (default 50, max 250)
`query`	No	Filter by name or email
`cursor`	No	Next page cursor
`orderBy`	No	Sort: createdAt \| updatedAt	updatedAt

save_commentInspect

Create or update a comment on a Linear issue. If id is provided, updates the existing comment; otherwise creates a new one. When creating, issueId and body are required.

ParametersJSON Schema

Name	Required	Description
`id`	No	Comment ID. If provided, updates the existing comment
`body`	Yes	Content as Markdown
`issueId`	No	Issue ID or identifier (e.g., LIN-123) (required when creating)
`parentId`	No	Parent comment ID (for replies, only when creating)

save_issueInspect

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.

ParametersJSON Schema

Name	Required	Description
`id`	No	Issue ID or identifier (e.g., LIN-123). If provided, updates the existing issue
`team`	No	Team name or ID (required when creating)
`cycle`	No	Cycle name, number, or ID
`links`	No	Link attachments to add [{url, title}]. Append-only; existing links are never removed
`state`	No	State type, name, or ID
`title`	No	Issue title (required when creating)
`blocks`	No	Issue IDs/identifiers this blocks. Append-only; existing relations are never removed
`labels`	No	Label names or IDs
`dueDate`	No	Due date (ISO format)
`project`	No	Project name, ID, or slug
`assignee`	No	User ID, name, email, or "me". Null to remove
`delegate`	No	Agent name or ID. Null to remove
`estimate`	No	Issue estimate value
`parentId`	No	Parent issue ID or identifier (e.g., LIN-123). Null to remove
`priority`	No	0=None, 1=Urgent, 2=High, 3=Normal, 4=Low
`blockedBy`	No	Issue IDs/identifiers blocking this. Append-only; existing relations are never removed
`milestone`	No	Milestone name or ID
`relatedTo`	No	Related issue IDs/identifiers. Append-only; existing relations are never removed
`description`	No	Content as Markdown
`duplicateOf`	No	Duplicate of issue ID/identifier. Null to remove

save_milestoneInspect

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.

ParametersJSON Schema

Name	Required	Description
`id`	No	Milestone name or ID
`name`	No	Milestone name (required when creating)
`project`	Yes	Project name, ID, or slug
`targetDate`	No	Target completion date (ISO format, null to remove)
`description`	No	Milestone description

save_projectInspect

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.

ParametersJSON Schema

Name	Required	Description
`id`	No	Project ID. If provided, updates the existing project
`icon`	No	Icon emoji (e.g., :eagle:)
`lead`	No	User ID, name, email, or "me". Null to remove
`name`	No	Project name (required when creating)
`color`	No	Hex color
`state`	No	Project state
`labels`	No	Label names or IDs
`summary`	No	Short summary (max 255 chars)
`addTeams`	No	Team name or ID to add
`priority`	No	0=None, 1=Urgent, 2=High, 3=Medium, 4=Low
`setTeams`	No	Replace all teams with these. Cannot combine with addTeams/removeTeams
`startDate`	No	Start date (ISO format)
`targetDate`	No	Target date (ISO format)
`description`	No	Content as Markdown
`removeTeams`	No	Team name or ID to remove
`addInitiatives`	No	Initiative names/IDs to add
`setInitiatives`	No	Replace all initiatives with these. Cannot combine with addInitiatives/removeInitiatives
`removeInitiatives`	No	Initiative names/IDs to remove

search_documentationInspect

Search Linear's documentation to learn about features and usage

ParametersJSON Schema

Name	Required	Description	Default
`page`	No	Page number
`query`	Yes	Search query

update_documentInspect

Update an existing Linear document

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Document ID or slug
`icon`	No	Icon emoji
`color`	No	Hex color
`title`	No	Document title
`content`	No	Content as Markdown
`project`	No	Project name, ID, or slug

Verify Ownership

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.

Server Details

Available Tools

Verify Ownership

Discussions

Your Connectors

Resources