mcp-server-linear
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 0 of 4 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y mcp-server-linear@1.6.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
4 tools that take no input and look read-only were called once with nothing. 0 returned a result.
linear_search_issues | No usable answer MCP error -32603: Failed to search issues: MCP error -32600: Not authenticated. Call linear_auth first. |
linear_get_teams | No usable answer MCP error -32603: Failed to get teams: MCP error -32600: Not authenticated. Call linear_auth first. |
linear_get_user | No usable answer MCP error -32603: Failed to get user info: MCP error -32600: Not authenticated. Call linear_auth first. |
linear_list_projects | No usable answer MCP error -32603: Failed to list projects: MCP error -32600: Not authenticated. Call linear_auth first. |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
linear_auth_callback code
Handle OAuth callback
linear_create_issue title, description, teamId, parentId, labelIds, assigneeId, priority, createAsUser, displayIconUrl
Create a new issue in Linear
linear_create_project_with_issues project, issues
Create a new project with associated issues. Note: Project requires teamIds (array) not teamId (single value).
linear_bulk_update_issues issueIds, update
Update multiple issues at once
linear_edit_issue issueId, title, description, stateId, priority, assigneeId, labelIds, projectId, projectMilestoneId, estimate, dueDate, parentId, sortOrder
Edit an existing issue, updating any of its fields. Note: When setting projectMilestoneId, you must also set projectId.
19 more tools
linear_search_issues query, teamIds, assigneeIds, states, priority, first, after, orderBy
Search for issues with filtering and pagination
linear_search_issues_by_identifier identifiers
Search for issues by their identifiers (e.g., ["ENG-78", "ENG-79"])
linear_get_issue identifier
Get a single issue by identifier, including all comments
linear_get_teams
Get all teams with their states and labels
linear_get_user
Get current user information
linear_delete_issue id
Delete an issue
linear_get_project id
Get project information
linear_list_projects filter
List all projects or filter them by criteria
linear_create_issues issues
Create multiple issues at once
linear_create_comment body, issueId
Creates a new comment on an issue
linear_update_comment id, input
Updates an existing comment
linear_delete_comment id
Deletes a comment
linear_resolve_comment id, resolvingCommentId
Resolves a comment
linear_unresolve_comment id
Unresolves a comment
linear_create_customer_need_from_attachment attachmentId, title, description, teamId
Creates a new customer need from an attachment
linear_get_project_milestones projectId, filter, first, after, last, before, includeArchived, orderBy
Get milestones for a project with filtering and pagination
linear_create_project_milestone projectId, name, description, targetDate, sortOrder
Create a new project milestone
linear_update_project_milestone id, name, description, targetDate, sortOrder
Update a project milestone
linear_delete_project_milestone id
Delete a project milestone
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=16.0.0 |
| Source | github.com/dvcrn/mcp-server-linear |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-U5yZsNOImvL0S1P8BqDOFDKJXxgI8HjEx7fbvGEuS3W/orKIwF/hw+wGYmjT+A/M2UUSbjVTcTkrZ0w4uZmRFw== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/mcp-server-linear)
New version out? Ask for a fresh report.