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 from https://linear.app/settings/account/security |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linear_create_issueC | Create a new Linear issue |
| linear_update_issueC | Update an existing Linear issue |
| linear_search_issuesC | Search issues in Linear with flexible filtering |
| linear_get_user_issuesC | Get issues assigned to a user |
| linear_add_commentC | Add a comment to a Linear issue |
| linear_get_teamsC | Get teams in the organization |
| linear_get_projectsC | Get projects in the organization |
| linear_get_project_issuesC | Get issues for a specific project |
| linear_get_team_issuesC | Get issues for a specific team |
| linear_get_viewerB | Get information about the authenticated user |
| linear_get_projectC | Get details about a specific project |
| linear_get_teamB | Get details about a specific team |
| linear_get_labelsB | Get labels from Linear, optionally filtered by team |
| linear_create_labelC | Create a new label in Linear |
| linear_update_labelC | Update an existing label in Linear |
| linear_add_attachmentC | Add an attachment to an issue in Linear |
| linear_get_attachmentsC | Get attachments for an issue in Linear |
| linear_link_issuesC | Create a relationship between issues in Linear |
| linear_get_issue_relationsC | Get relationships for an issue in Linear |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| linear_bug_report | Creates a bug report in Linear |
| linear_feature_request | Creates a feature request in Linear |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| linear-organization | Linear organization information |
| linear-viewer | Current Linear user |
| linear-viewer-teams | Current Linear user's teams |
| linear-viewer-projects | Current Linear user's projects |
| linear-viewer-assigned | Issues assigned to the current Linear user |
| Linear Label | View details for a Linear label |
| Linear Milestone | View details for a Linear milestone |
| Linear Attachment | View details for a Linear attachment |
TDQS
Scored across 19 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in Linear's domain. For example, linear_get_team_issues retrieves issues for a team, while linear_get_user_issues gets issues assigned to a user, and linear_search_issues allows flexible filtering across all issues. No tools appear to overlap or cause confusion.
All tools follow a consistent 'linear_verb_noun' pattern with snake_case throughout. The verbs are clear and appropriate (e.g., get, create, update, add, link, search), and the nouns specify the target resource (e.g., issue, label, project, team). This predictability makes the tool set easy to navigate.
With 19 tools, this server is well-scoped for managing Linear's core entities like issues, projects, teams, labels, and attachments. Each tool earns its place by covering essential CRUD operations and queries without redundancy, fitting the typical range of 3-15 tools for a comprehensive API integration.
The tool surface provides complete coverage for Linear's domain, including CRUD for issues and labels, attachment and comment management, relationship linking, and queries for projects, teams, and users. There are no obvious gaps; agents can perform full lifecycle operations without dead ends.