linear_get_issue
Fetch details of a single Linear issue by providing its URL or identifier.
LABSCO SUMMARY
Two read tools and nothing else, which reads as a decision rather than a gap.
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.
What it is
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.
What you get
- 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.
Requirements
A LINEAR_API_TOKEN for the Linear workspace holding the issue. Both tools address an issue by its URL or its identifier.
Setup effort
One command plus a key — npx -y @keegancsmith/linear-issues-mcp-server, then supply credentials
USE CASES
01
Reading the ticket someone linked you to
Paste the Linear URL from the message and pull the issue itself, without opening the board to find it.
02
Catching up on a thread before replying
Pull the issue with its whole comment history, so the reasoning that lives in the discussion arrives with the description rather than after it.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
linear_get_issue_with_comments
Fetch a Linear issue with all its comments and complete information.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
- npx on PATH
- LINEAR_API_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @keegancsmith/linear-issues-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"linear-issues": {
"command": "npx",
"args": [
"-y",
"@keegancsmith/linear-issues-mcp-server"
],
"env": {
"LINEAR_API_TOKEN": "<YOUR_LINEAR_API_TOKEN>"
}
}
}
}
