mcp-linear
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_teamsA | List Linear teams as {key, name}. Team keys are the prefix of issue identifiers, e.g. the GOV in GOV-123. |
| list_statesA | List the workflow states for a team, in workflow order, as {name, type}.
These names are what create_issue and update_issue accept for |
| list_labelsA | List the issue labels that can be applied to an issue, as {name}.
team: optional team key or full team name. With a team, returns that team's
own labels followed by the workspace-wide labels; without one, the
workspace-wide labels only. Names are what create_issue and update_issue
accept for |
| list_usersA | List active Linear users as {name, email}. |
| get_issueA | Fetch a Linear issue by its human identifier, e.g. "GOV-123". Returns title, description, state, assignee, team, priority, labels, URL, and the git branch name Linear suggests for the issue. |
| list_my_issuesA | List issues assigned to the owner of the configured API key, most recently
updated first.
state: optional state-name filter, e.g. "In Progress". Case-insensitive.
The filter is applied after the fetch, so passing one makes the server
over-fetch (four times |
| search_issuesA | Full-text search over Linear issues, with optional filters.
team: team key or full team name, e.g. "GOV" or "Governance".
state: workflow state name, e.g. "In Progress". Resolved against the team's
workflow when |
| get_commentsA | Fetch the comments on a Linear issue, oldest first. identifier: human issue identifier, e.g. "GOV-123". |
| add_commentA | Post a comment on a Linear issue. Markdown is supported. identifier: human issue identifier, e.g. "GOV-123". |
| create_issueA | Create a Linear issue. Returns the created issue including its new identifier. team: team key or name, e.g. "GOV". assignee: user display name or email. See list_users. state: workflow state name, e.g. "Backlog". See list_states. priority: 0 none, 1 urgent, 2 high, 3 medium, 4 low. labels: label names on that team. See list_labels. |
| update_issueA | Update fields on an existing Linear issue. Only the fields you pass are changed. identifier: human issue identifier, e.g. "GOV-123". state, assignee, labels: names, resolved against the issue's own team. priority: 0 none, 1 urgent, 2 high, 3 medium, 4 low. Passing labels replaces the issue's labels entirely. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct resource or action: list_* clearly separates teams, states, labels, users, and my issues, while get_issue, search_issues, and list_my_issues offer different retrieval modes. Comments, creation, and updates are also cleanly separated with no overlapping responsibilities.
The tools consistently follow a verb_noun snake_case pattern: list_teams, list_states, get_issue, create_issue, update_issue, add_comment, and so on. list_my_issues is a minor variation but still predictable and fits the overall naming logic.
With 11 tools, the server is well-scoped for a Linear issue-management integration. It provides reference lookups, issue operations, and comments without redundant or unnecessary tools.
The core issue lifecycle is covered: create, get, update, search, list-my-issues, and comments, plus supporting lookups for teams, states, labels, and users. Obvious gaps like deleting/archiving issues or listing all issues in a team are minor and can often be worked around with search_issues.