Use the API-key path — the README marks the OAuth alternative as not implemented, so a personal key is the working route. Bulk issue updates are listed as implemented but still in testing, and comment threads, label management, complex search filters and pagination are all listed as in development. If your workflow leans on any of those, try them before you build around this.
A Linear MCP server you build from source and launch locally. It talks to Linear's API on behalf of your client and covers issues, projects and teams.
- Create issues with the full field set — title, description, team, project — and update or delete them, one at a time or in bulk
- Search issues with filtering, and associate them with a project
- Create parent/child relationships between issues
- Create a project together with its issues, and read project information back
- Read team information, including workflow states and labels
Build it yourself: clone the repo, `npm install`, `npm run build`. The package is linear-mcp, version 1.0.0, and the client launches it as `node /path/to/linear-mcp/build/index.js`. Authentication is a Linear personal API key — Settings, then "Security & access", then "Personal API keys" — passed to the server as `LINEAR_API_KEY`.
One command plus a key — npx -y linear-mcp, then supply credentials