mcp-server-linear
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINEAR_API_KEY | No | Linear personal API key | |
| LINEAR_OAUTH_CLIENT_ID | No | OAuth client ID | |
| LINEAR_OAUTH_CLIENT_SECRET | No | OAuth client secret |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| projectsA | Get all projects in Linear |
| projectB | Get a single project in Linear |
| issueC | Get a single issue in Linear |
| project_statusesA | Get all available project statuses in Linear |
| issue_statesA | Get all available issue states (workflow states) in Linear |
| project_issuesC | Get all issues in a project in Linear |
| issue_labelsA | Get all issue labels in Linear |
| create_issueB | Create a new issue in Linear |
| update_issueB | Update an existing issue in Linear |
| delete_issueB | Delete an existing issue in Linear |
| update_issue_labelsB | Update the labels of an existing issue in Linear |
| update_issue_priorityB | Update the priority of an existing issue in Linear |
| update_issue_estimateB | Update the estimate of an existing issue in Linear |
| update_issue_stateB | Update the state of an existing issue in Linear |
| create_commentB | Create a new comment in Linear |
| update_commentA | Update an existing comment in Linear |
| delete_commentC | Delete an existing comment in Linear |
| get_issue_commentsB | Get comments for a specific issue in Linear |
| get_viewerA | Get current user information including teams |
| search_issuesC | Search for issues with advanced filtering options |
| update_project_stateB | Update the state of an existing project in Linear |
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 21 tools
Every tool has a distinct purpose focusing on issues, comments, projects, or viewer info. No overlaps exist; each action-resource pair is unique.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_issue, update_issue_priority). No mixing of styles.
21 tools is on the higher side but still within a manageable range for a comprehensive project management server. Each tool seems justified.
CRUD is complete for issues and comments, but project creation/deletion is missing. Also lacking team management tools, leaving notable gaps.