Linear MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOOL_PREFIX | No | Optional prefix for tool names when using multiple Linear workspaces | |
| LINEAR_ACCESS_TOKEN | Yes | Your Linear API token (developer token or 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_auth_callbackC | Handle OAuth callback |
| linear_create_issueB | 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_issuesB | Update multiple issues at once |
| linear_edit_issueA | Edit an existing issue, updating any of its fields. Note: When setting projectMilestoneId, you must also set projectId. |
| linear_search_issuesB | Search for issues with filtering and pagination |
| linear_search_issues_by_identifierA | Search for issues by their identifiers (e.g., ["ENG-78", "ENG-79"]) |
| linear_get_issueA | Get a single issue by identifier, including all comments |
| 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_get_projectC | Get project information |
| linear_list_projectsB | List all projects or filter them by criteria |
| linear_create_issuesC | Create multiple issues at once |
| linear_create_commentC | Creates a new comment on an issue |
| linear_update_commentC | Updates an existing comment |
| linear_delete_commentB | Deletes a comment |
| linear_resolve_commentC | Resolves a comment |
| linear_unresolve_commentC | Unresolves a comment |
| linear_create_customer_need_from_attachmentC | Creates a new customer need from an attachment |
| linear_get_project_milestonesC | Get milestones for a project with filtering and pagination |
| linear_create_project_milestoneC | Create a new project milestone |
| linear_update_project_milestoneC | Update a project milestone |
| linear_delete_project_milestoneB | Delete a project milestone |
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 24 tools
Each tool targets a distinct resource and action (e.g., issue, comment, project, milestone, team, user). There is no overlap; even comment actions (create, delete, resolve, unresolve, update) are clearly separated.
All tools follow the pattern 'linear_<verb>_<resource>' with underscores and lowercase. Verbs like create, get, list, search, update, delete are used consistently. The naming is predictable and unambiguous.
24 tools is a bit above the typical 3-15 range but still reasonable for a project management server covering multiple entities (issues, comments, projects, milestones). It feels slightly heavy but not excessive.
Core CRUD for issues, comments, and milestones is covered. However, missing update/delete for projects and a dedicated get comment tool (comments are only accessible via get_issue) are minor gaps that agents can work around.