It fetches a Linear issue by URL or identifier, optionally with its comment thread, and it cannot create, update, assign or close anything. If what you want is an agent that can read the ticket it was pointed at without also being able to move your board, the small surface is the feature; if you want it to file the follow-up, this is not the server that will.
A read-only Linear reader with 2 tools: linear_get_issue returns one issue's details, and linear_get_issue_with_comments returns the same issue with all its comments and complete information.
- linear_get_issue takes an issue URL or identifier, so a link dropped into the conversation is enough to pull the issue with no lookup step in between.
- linear_get_issue_with_comments returns the issue together with all its comments, which is the one to reach for when the decision you need was made in the thread rather than written into the description.
- Addressing is by the URL or identifier a person would paste, not by an internal id you would have to go and find.
A LINEAR_API_TOKEN for the Linear workspace holding the issue. Both tools address an issue by its URL or its identifier.
One command plus a key — npx -y @keegancsmith/linear-issues-mcp-server, then supply credentials