# Linear — MCP server on mcp.ai
> Linear via linguagem natural: crie, busque e atualize issues, projetos e comentários. Plataforma fornece a aplicação OAuth, você só clica em Conectar e autoriza seu workspace Linear. Vários workspaces podem ser conectados no mesmo MCP.

By: mcp.ai · official
Page: https://mcp.ai/linear

## Connect (MCP protocol)
Remote MCP endpoint (HTTP, streamable): https://api.mcp.ai/p_linear?ms=1781044500000
Add it as a custom/remote MCP connector, then authenticate when prompted.

## REST API (no MCP client required)
Every tool is also a REST endpoint, authed with a workspace API key.
Discover: GET https://api.mcp.ai/api/linear/_endpoints   # public; lists every endpoint
Call:     POST https://api.mcp.ai/api/linear/<endpoint>
  Authorization: Bearer sk_live_…   # create one at https://mcp.ai/settings/api-keys
  Content-Type: application/json
  Body: { …args }   →   { "ok": true, "tool": "<id>", "result": { … } }

## Developer docs
How to use (MCP or REST), markdown: https://mcp.ai/linear/skill.md
Postman collection (v2.1): https://mcp.ai/linear/postman.json

## Tools
- linear_create_linear_attachment(url: string, title: string, issue_id: string, subtitle: string) — Creates a new attachment and associates it with a specific, existing linear issue.
- linear_create_linear_comment(body: string, issue_id: string) — Creates a new comment on a specified linear issue.
- linear_create_linear_issue(title: string, team_id: string, cycle_id?: string, due_date?: string, estimate?: integer, priority?: integer, state_id?: string, label_ids?: string[], parent_id?: string, project_id?: string, assignee_id?: string, description?: string) — Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
- linear_create_linear_issue_details(team_id: string) — Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
- linear_create_linear_label(name: string, color: string, team_id: string, description?: string) — Creates a new label in linear for a specified team, used to categorize and organize issues.
- linear_delete_linear_issue(issue_id: string) — Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
- linear_get_all_linear_teams() — Retrieves all teams from the linear workspace without requiring any parameters.
- linear_get_attachments(issue_id: string, file_name: string, attachment_id: string) — Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
- linear_get_current_user() — Gets the currently authenticated user's id, name, email, and other profile information. use this to identify 'me' in other linear operations that require user id filtering.
- linear_get_cycles_by_team_id(team_id: string) — Retrieves all cycles for a specified linear team id; cycles are time-boxed work periods (like sprints) and the team id must correspond to an existing team.
- linear_get_linear_issue(issue_id: string) — Retrieves an existing linear issue's comprehensive details, including title, description, attachments, and comments.
- linear_list_linear_cycles() — Retrieves all cycles (time-boxed iterations for work) from the linear account; no filters are applied.
- linear_list_linear_issues(after?: string, first?: integer, project_id?: string, assignee_id?: string) — Lists non-archived linear issues; if project id is not specified, issues from all accessible projects are returned. can also filter by assignee id to get issues assigned to a specific user.
- linear_list_linear_labels(team_id: string) — Retrieves all labels associated with a given team id in linear; the team id must refer to an existing team.
- linear_list_linear_projects() — Retrieves all projects from the linear account.
- linear_list_linear_states(team_id: string) — Retrieves all workflow states for a specified team in linear, representing the stages an issue progresses through in that team's workflow.
- linear_list_linear_teams(project_id: string) — Retrieves all teams, including their members, and filters each team's associated projects by the provided 'project id'.
- linear_list_linear_users(after?: string, first?: integer) — Lists all users in the linear workspace with their ids, names, emails, and active status.
- linear_remove_issue_label(issue_id: string, label_id: string) — Removes a specified label from an existing linear issue using their ids; successful even if the label isn't on the issue.
- linear_run_query_or_mutation(variables: object, query_or_mutation: string) — Wildcard action that executes any graphql query or mutation against the linear api. use this as a fallback when no specific action exists for your use case, or when you need to perform complex operati
- linear_update_issue(title?: string, team_id?: string, due_date?: string, estimate?: integer, issue_id: string, priority?: integer, state_id?: string, label_ids?: string[], parent_id?: string, project_id?: string, assignee_id?: string, description?: string) — Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.

## Example prompts
- "Crie uma issue 'Corrigir login no Safari' no time de Engenharia"
- "Liste minhas issues abertas com prioridade alta"
- "Comente 'Em revisão' na issue ENG-142"

## Links
Docs: https://mcp.ai/docs/mcps/linear
Website: https://mcp.ai/mcps/linear