Compared · linear
7 Linear MCP servers. Which one to use.
Every Linear server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 7 servers, mostly mirrored from the MCP registry as of 2026-09-08. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Linear Project | org.openlyuseful | no flag | REVIEW | 90 | npm @openly-useful/linear-project-mcp-server |
| Linear | app.linear | no flag | REVIEW | 85 | remote endpoint |
| io.usefulapi/linear | io.usefulapi | no flag | REVIEW | 83 | remote endpoint |
| Linear MCP (multi-workspace, PAT auth) | io.github.adelaidasofia | no flag | REVIEW | 79 | pypi adelaidasofia-linear-mcp |
| Linear | io.github.pipeworx-io | no flag | REVIEW | 77 | remote endpoint |
| Linear-Task-Broker | io.github.Evozim | no flag | REVIEW | 75 | remote endpoint |
| io.github.toolwright-adk/linear-bootstrap | io.github.toolwright-adk | no flag | REVIEW | 68 | npm @toolwright-adk/linear-bootstrap |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.