Linear

Linear does not publish a standalone npm server. The supported setup is mcp-remote pointed at https://mcp.linear.app/mcp, which bridges a local stdio MCP client to Linear's hosted endpoint. The tool surface is controlled by Linear so it stays in sync with API changes — no package to update on your side. What it does: - Full issue, project, cycle, and team CRUD against the Linear GraphQL API - Comment, sub-issue, and priority management with no client-side ID juggling - Cycle and roadmap queries for status-update workflows - Server-sent events streaming for long-running queries so partial results arrive first - OAuth browser flow on first invocation, refresh tokens cached by the bridge - Works in Claude Desktop, Cursor, Claude Code, and any MCP client that supports stdio Example: Ask "which issues in the current cycle are blocked on review, and which on-call teammate owns the reviewer role this week" — Linear composes this from issue, team-membership, and cycle queries in a single MCP session. The user never copies an issue ID. Setup: Point your MCP client at "npx -y mcp-remote https://mcp.linear.app/mcp". On first invocation the bridge opens a browser for OAuth consent, then caches the token locally. Nothing to self-host. Transport: stdio locally via mcp-remote, which proxies to Streamable HTTP at Linear's endpoint. Notes: No self-hosting and no offline mode. If you need offline use, the community cosmix/linear-mcp server talks to the Linear API directly, but you manage tokens and tool drift yourself. Because Linear controls the tool surface, server-side tool changes can appear between client restarts — pin no packages on your side but do expect the available toolset to evolve.