Linear
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINEAR_API_KEY | Yes | Your Linear personal API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linear_authC | Initialize OAuth flow with Linear |
| linear_auth_callbackC | Handle OAuth callback |
| linear_create_issueC | Create a new issue in Linear |
| linear_create_project_with_issuesB | Create a new project with associated issues. Note: Project requires teamIds (array) not teamId (single value). |
| linear_bulk_update_issuesC | Update multiple issues at once |
| linear_search_issuesB | Search for issues with filtering and pagination |
| linear_get_teamsA | Get all teams with their states and labels |
| linear_get_userB | Get current user information |
| linear_delete_issueC | Delete an issue |
| linear_delete_issuesC | Delete multiple issues |
| linear_get_projectC | Get project information |
| linear_search_projectsC | Search for projects by name |
| linear_create_issuesA | Create multiple issues at once |
| linear_get_issue_commentsA | Get comments for a specific issue, including threaded replies |
| linear_create_commentA | Create a new comment on an issue or reply to an existing comment |
| linear_create_project_milestoneC | Create a new project milestone in Linear |
| linear_update_project_milestoneB | Update an existing project milestone |
| linear_delete_project_milestoneB | Delete a project milestone |
| linear_get_project_milestoneC | Get information about a specific project milestone |
| linear_search_project_milestonesB | Search for project milestones with filtering and pagination |
| linear_get_project_milestonesC | Get all milestones for a specific project |
| linear_create_project_milestonesA | Create multiple project milestones at once |
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 22 tools
Most tools are clearly distinct by resource and action (e.g., issues vs. projects vs. milestones). The few potentially confusable pairs are singular/plural variants like create_issue/create_issues and delete_issue/delete_issues, but the plural forms clearly indicate bulk operations.
All tools use a consistent linear_ prefix followed by snake_case verb_noun patterns (e.g., create_issue, search_projects, get_project_milestones). The singular/plural distinction is applied uniformly, and there are no mixed conventions or vague verbs.
At 22 tools, the count falls into the borderline-heavy range (16-25). However, the coverage spans multiple subdomains (issues, projects, milestones, comments, auth, teams, user), so the count is defensible but feels slightly high for an MCP server.
Issues have create, update (bulk), delete, and search, but no single-issue get; projects support create/get/search but not update or delete; comments only support get and create. These are notable gaps in lifecycle coverage for the core resources.