Access, search, and manage Linear issues, projects, and comments.
This tool is described as managing Linear resources and has the usual local execution characteristics of an MCP server. The materials do not disclose required credentials or remote endpoints, but the claimed CRUD access to an external service conflicts with the sparse metadata, so verification is needed before use. Open-source code under MIT is a positive sign, but low adoption and unknown maintenance keep the overall posture at cautious rather than high risk.
Metadata says no credentials are required, but the tool claims full CRUD management of Linear resources, which would normally require Linear access credentials. The authentication model is not explained, so there is a caution-level disclosure gap; verify whether a token is requested at runtime.
No remote endpoint is listed in metadata, but the description implies access to remote Linear resources such as issues, projects, and comments. That likely involves sending user input and resource content to an external service. Since endpoints and transfer scope are not documented, confirm it only talks to official Linear-related APIs.
The system flags that this tool executes code/processes, which is a normal local capability for MCP tools. The materials do not show requests for elevated system privileges or execution behavior clearly beyond its stated purpose. This is caution based on inherent capability, not high risk.
The description indicates search plus full CRUD over Linear resources, so its data access scope at minimum covers business data such as issues, projects, and comments. The materials do not mention local file access scope, and there is no explicit sign of overbroad authorization. The main concern is broad read/write access to remote business data, so use least privilege.
The repository is open source under MIT, making the code auditable in principle, which lowers risk. However, it comes from a third-party registry, has 0 stars, unknown maintenance status, and no README, limiting verifiability and maturity. No concrete malicious red flags are present, so this should not be elevated to high risk.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-server-linear" yet — see the docs or source repo.
Search Linear for all issues assigned to me with status Todo or In Progress, sort them by priority, and list the title, project, due date, and issue link.
A filtered issue list for quickly planning the day's work.
Create a Linear project named "Q3 User Growth Experiments" with the description "Track this quarter's growth hypotheses and experiment progress," then create 3 issues: design experiment plan, set up analytics tracking, and analyze first-round results.
A new project with starter issues so the team can begin collaborating immediately.
Find the most recent Linear issue with "payment retry failure" in the title and add this comment: Root cause identified as third-party API timeouts; today we will add retry logic and alerts, with a fix expected by tomorrow afternoon.
A new progress comment added to the target issue for team visibility.
Connect to Linear to search, create, update, and comment on work items.
Manage Linear issues, projects, and teams through MCP-powered AI workflows.
Manage Linear issues, projects, and workspaces with natural language.
Manage Linear issues, comments, assignments, and new tickets through MCP tools.
Quickly search and filter Linear issues, users, teams, and states locally.
Self-hosted Linear MCP with minimal fields to cut tokens and agent costs.