LabscoMCP early access ↗
tacticlaunchMCP SERVER

Linear MCP by tacticlaunch

Work a Linear workspace from your client: file and move issues, run cycles, cut releases with notes, attach customer needs to the roadmap, and administer the webhooks, saved views and OAuth applications behind it.

Project & Task ManagementCommunity

LABSCO SUMMARY

The parts of Linear that normally stay in the web app — release pipelines, customer needs, audit events — arrive here as tools.

Most Linear servers stop at issues and cycles; this one carries releases, initiatives, customers and workspace administration too, which is why the surface reaches 198 tools and why a client on a tight tool budget will feel it. A few tools behave more narrowly than their names suggest: completing a release needs the pipeline to already have a completed stage configured, and a client-credentials token comes back once, without a refresh token, normally valid for 30 days. The managed OAuth application tools are alpha and reach only child applications the calling app owns.

What it is

A server over Linear's GraphQL API with 198 tools, reaching past issues and cycles into release pipelines, roadmaps, initiatives, customers, workspace documents and OAuth application management. It also publishes Linear resources by URI and a few ready-made prompts.

What you get

  • Issues filed, updated, searched, assigned, prioritised, transferred between teams, duplicated, converted to subtasks and related to one another as blocks or is-blocked-by, with labels added and removed one at a time
  • Cycles run end to end: the active cycle for a team, its issues filtered by state or assignee, cycle statistics and completion, alongside project updates that carry a health value
  • Release pipelines with their stages, releases stamped with a version and a commit SHA, and release notes composed either from explicit release IDs or from a range between two releases
  • Customers and customer needs, each need linked to an issue or a project, or created straight from an attachment that already exists
  • Workspace documents read and searched across teams, projects, initiatives, cycles, releases and issues, with the content history behind a document
  • Administration a token can do without the web app: webhooks and their signing secrets, saved views, team memberships, organization and per-user audit events, and revoking authentication sessions
  • Linear's own OAuth surface: an authorization URL, app-actor tokens through the client_credentials grant, and alpha child applications whose client and webhook secrets can be rotated
  • Resources and prompts alongside the tools — the viewer, teams, a project's issues or documents as attachable resources, and ready-made prompts for a project summary, a project update draft or an issue triage

Requirements

Node 20 or newer and a Linear credential in LINEAR_API_TOKEN — a personal API key from Security & access covers issues, cycles, documents and workspace webhooks. Managing child OAuth applications needs the server authenticated as an OAuth application instead, so a personal key can only prepare the manifest and setup URL for an administrator to submit. One process uses one credential, so a setup that needs both usually runs two server entries. The tools that return secret material require explicit confirmation flags, and webhook URLs have to be publicly reachable HTTPS. MIT.

Setup effort

One command plus a key — npx add-mcp @tacticlaunch/mcp-linear --env LINEAR_API_TOKEN=<YOUR_LINEAR_API_TOKEN>

See installation options