Because it runs on Linear's official SDK, the parts that usually break in a hand-rolled wrapper — parent/child team inheritance, label sync, cycle filters — come back already correct, so an agent can go from 'what is in this cycle' to a filed subissue in one pass.
An MCP server built on Linear's official SDK. It talks to Linear with your personal API key and hands back issues with their relationships — parent, children, labels, cycle — already resolved.
- An issue fetched by ID or key, with its relationships on request
- New issues and subissues, with labels attached and team inherited from the parent
- Existing issues updated across their fields, and assigned to yourself with the keyword `me`
- Search using Linear's own filters, including by cycle — current, next, previous, or a specific cycle by number or UUID
- Comments added to issues in markdown
- Projects listed, project updates read, and a new project update posted with a health status
Bun v1.0.0 or higher, and a Linear account with API access. The personal API key goes in the environment — one variable. Clone and `bun run build`, then point your client at the built `index.js` — there is no npx path.
