Linear MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINEAR_API_KEY | Yes | Your Linear Personal API key, obtained from Linear workspace settings under Settings > API > Personal API keys. |
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_get_issuesC | Get issues from a specific team |
| linear_search_issuesC | Search for issues using a query |
| linear_create_issueC | Create a new issue in a team |
| linear_update_issueC | Update an existing issue |
| linear_add_commentC | Add a comment to an issue |
| linear_get_teamsC | List all teams in the workspace |
| linear_get_usersC | List all users in the workspace |
| linear_get_workflow_statesC | Get workflow states for a specific team |
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 8 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Linear domain, such as creating issues, getting issues, adding comments, updating issues, searching issues, and retrieving teams, users, and workflow states. There is no ambiguity or overlap in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent 'linear_verb_noun' pattern with snake_case, such as linear_create_issue, linear_get_issues, and linear_update_issue. This predictability enhances readability and usability for agents, with no deviations in naming conventions.
With 8 tools, the server is well-scoped for managing issues and related resources in Linear, covering core operations like CRUD for issues, commenting, searching, and retrieving teams, users, and states. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides strong coverage for issue management, including create, get, update, comment, and search, along with essential context tools for teams, users, and workflow states. A minor gap is the lack of delete operations for issues or other resources, but agents can work around this with updates or other methods.