MCP Linear

What tacticlaunch/mcp-linear MCP server does

The tacticlaunch/mcp-linear MCP server connects MCP-compatible AI clients to Linear's GraphQL API. It covers day-to-day project-management tasks as well as administrative workflows that are not limited to creating, reading, updating, and deleting issues.

Agents can retrieve issues, teams, projects, cycles, milestones, roadmaps, customers, customer needs, and documents associated with several Linear object types. They can create and modify issues, update status and assignees, add comments, manage projects and initiatives, work with saved views and favorites, and handle templates, custom fields, and attachments.

The server also exposes operations for workspace webhooks, OAuth application setup, scoped client-credentials tokens, customer records, notifications, subscriptions, sessions, audits, integrations, rate limits, and server health. Some OAuth and secret-management operations require specific Linear credentials and explicit confirmation flags.

How it works

The tacticlaunch/mcp-linear MCP server runs locally as an MCP stdio process. An MCP client launches the mcp-linear executable and passes a Linear credential through an environment variable or command-line option. The server then translates MCP requests into Linear GraphQL API operations.

In addition to tools, it publishes MCP resources such as the current viewer, organization, teams, projects, individual issues, documents, roadmaps, milestones, and rate-limit information. Built-in prompts support project-status summaries, project-update drafts, issue triage, and document summaries.

Each process uses one Linear credential. A personal API key supports normal Linear and workspace-webhook operations, while managing child OAuth applications requires an eligible OAuth application's access token. Webhook destinations must use publicly reachable HTTPS URLs.

Setup and configuration

Install the package with a package runner or configure it directly in an MCP client's settings. A manual stdio configuration uses npx with the @tacticlaunch/mcp-linear package and supplies LINEAR_API_TOKEN in the environment.

The alternative OAuth environment variable is LINEAR_OAUTH_ACCESS_TOKEN. Command-line options --token and --oauth-token can be used instead, and explicit command-line credentials take precedence. When both environment credential types are present, OAuth authentication is selected.

The README lists Node.js 20 or newer and npm or Yarn as prerequisites. It provides configuration locations for Cursor and Claude Desktop, among other MCP-aware clients.

Tools and capabilities

The tacticlaunch/mcp-linear MCP server supports:

• Issue creation, updates, status changes, assignment, and comments.
• Project, initiative, milestone, roadmap, cycle, document, template, and saved-view workflows.
• Customer records, customer statuses and tiers, and customer needs linked to issues or projects.
• Workspace webhook creation, updates, and signing-secret rotation.
• OAuth manifests, authorization URLs, child OAuth applications, and scoped client-credentials tokens.
• MCP resources and prompts for project, issue, document, roadmap, milestone, and rate-limit data.

Limitations and notes

Personal API keys cannot call Linear's managed child-OAuth-application API. Client-credentials tokens generally expire after 30 days and do not include refresh tokens. Requesting a different scope set can revoke existing app-actor tokens, so the relevant token tool requires confirmation of secret exposure and scope-change risk.

Secrets returned during OAuth-app or webhook-secret operations are one-time values and should be moved directly into a secret manager. The server validates webhook URLs and rejects credentials in URLs along with loopback, private-network, link-local, and local-hostname destinations.