linear-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINEAR_API_KEY | Yes | Your Linear API key for authentication. | |
| LINEAR_MCP_READ_ONLY | No | Set to 'true' to run in read-only mode, preventing write operations. | false |
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 |
|---|---|
| list_issuesC | List issues with optional filters |
| list_teamsA | List all teams in the workspace |
| get_teamC | Get team details |
| list_projectsC | List all projects |
| get_projectC | Get project details |
| search_issuesC | Search for issues using query text |
| get_issueB | Get detailed information about a specific issue |
| list_roadmapsC | List all roadmaps |
| get_roadmapC | Get roadmap details |
| get_initiativeB | Get detailed information about a specific initiative |
| get_commentC | Get a specific comment |
| list_labelsB | List all labels in a team |
| get_labelC | Get label details |
| list_cyclesC | List all cycles in a team |
| get_cycleC | Get cycle details |
| list_documentsC | List all documents |
| get_documentC | Get document details |
| list_usersB | List all users in the workspace |
| get_userA | Get detailed information about a specific user |
| meA | Get information about the authenticated user |
| create_issueC | Create a new issue in Linear |
| update_issueC | Update an existing issue |
| create_commentB | Create a new comment on an issue |
| update_commentB | Update an existing comment |
| delete_commentB | Delete a comment |
| create_labelB | Create a new label in a team |
| update_labelB | Update an existing label |
| create_cycleC | Create a new cycle for a team |
| update_cycleC | Update an existing cycle |
| create_documentC | Create a new document |
| update_documentB | Update an existing document |
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 31 tools
Each tool targets a distinct resource-action pair (e.g., create_comment, get_issue), and there is no overlap in purpose. The 'me' tool is unique and clear.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_issues, create_cycle). The only outlier is 'me', which is a standard convention for user info.
With 31 tools, the server exceeds the recommended range of 3-15. While the tools cover many entities, the count feels heavy for a single MCP server.
The server provides create, get, list, and update for most resources, but notably lacks delete operations for issues, cycles, documents, and projects. This is a significant gap.