Linear MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINEAR_API_KEY | No | Your Linear personal API key for authentication | |
| LINEAR_CLIENT_ID | No | Your OAuth application client ID (alternative authentication method) | |
| LINEAR_REDIRECT_URI | No | OAuth redirect URI for callback | http://localhost:3000/callback |
| LINEAR_CLIENT_SECRET | No | Your OAuth application client secret (alternative authentication method) |
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_authC | Initialize OAuth flow with Linear |
| linear_auth_callbackC | Handle OAuth callback |
| linear_create_issueC | 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_issuesC | Update multiple issues at once |
| linear_search_issuesB | Search for issues with filtering and pagination |
| 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_delete_issuesC | Delete multiple issues |
| linear_get_projectC | Get project information |
| linear_search_projectsC | Search for projects by name |
| linear_create_issuesA | Create multiple issues at once |
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 13 tools
Most tools have distinct purposes targeting specific resources and actions, but there is some overlap between linear_create_issue and linear_create_issues, and between linear_delete_issue and linear_delete_issues, which could cause confusion about when to use the singular vs. plural versions. The descriptions clarify the bulk operations, but the naming similarity still creates minor ambiguity.
All tools follow a consistent snake_case naming pattern with a 'linear_' prefix and clear verb_noun structure (e.g., linear_create_issue, linear_search_issues). The naming is highly predictable and uniform across all 13 tools, making it easy for agents to understand and use them.
With 13 tools, the server is well-scoped for managing Linear issues, projects, teams, and users, covering core operations like CRUD, search, and bulk actions. Each tool appears to earn its place without feeling bloated or insufficient for the domain of project management and issue tracking.
The toolset provides strong coverage for issue and project management, including CRUD operations, search, and bulk actions, with no major dead ends. However, there are minor gaps, such as missing update operations for projects or teams, and no tools for managing issue comments or attachments, which could limit some workflows.