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 |
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_teamsA | List every team in the Linear workspace. Returns each team's identifier (key), human-readable name, and UUID. Use this first when you don't know a team's key. |
| list_cyclesA | List cycles (sprints) for a team. Cycles have per-team monotonic numbers (HYD-cycle-2 is different from another-team-cycle-2). Filter by scope to narrow to only past, current, or future cycles. |
| list_issues_in_cycleA | List issues in a Linear cycle. Provide EITHER cycle_id (from list_cycles) OR both team and cycle_number. Returns identifier, title, state, assignee, priority, estimate — enough to render a cycle overview. |
| get_issueA | Fetch full details for one Linear issue. Accepts either the human identifier (e.g. 'HYD-123') or the internal UUID. Returns description, state, assignee, cycle, labels, and the most recent comments. |
| search_issuesA | Search the workspace's issues by text. Matches title, description, and comments. Returns identifier, title, state, URL — shape aligned with list_issues_in_cycle so results can be treated the same way. |
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 5 tools
Each tool has a clearly distinct purpose: fetching a single issue, listing cycles, listing issues in a cycle, listing teams, and searching issues. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (get_issue, list_cycles, list_issues_in_cycle, list_teams, search_issues), making it predictable.
5 tools is well-scoped for a Linear workspace, covering the core entities (teams, cycles, issues) without unnecessary tools.
The set covers read operations comprehensively but lacks any create/update/delete tools for issues or other entities, which is a notable gap for a project management server.