Linear MCP Server

Name: Linear MCP Server
Author: cline

@cline

Repository

About Linear MCP Server

a private MCP server for accessing Linear

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "linear": {
      "command": "node",
      "args": [
        "/path/to/linear-mcp/build/index.js"
      ],
      "env": {
        "LINEAR_API_KEY": ""
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Linear MCP Server?

An MCP server for interacting with Linear's API. It provides a set of tools for managing Linear issues, projects, and teams through Cline.

How to use Linear MCP Server?

Clone the repository, install dependencies (npm install), copy .env.example to .env, and configure authentication using an API key from Linear Settings. Then build (npm run build) and start (npm start) the server. Integrate with Cline by adding the server configuration to your Cline MCP settings file.

Key features of Linear MCP Server

Create, update, delete, and search issues with full field support.
Manage projects with rich text descriptions using Linear's documentContent field.
Access team information, states, and labels.
Support for bulk issue creation and deletion.
API Key and OAuth authentication (OAuth not yet implemented).

Use cases of Linear MCP Server

Automate issue triage and updates directly from Cline.
Create and assign projects with rich descriptions.
Perform bulk operations on issues for project migration or cleanup.
Query team workflows and state information for reporting.

FAQ from Linear MCP Server

What authentication methods are supported?

API Key authentication (recommended) is fully implemented. OAuth flow is noted as an alternative but is not yet implemented.

What dependencies are required to run the server?

Node.js and npm are required. The server is built with npm and run using Node.

Where does the server store authentication tokens?

Authentication tokens are stored in a .env file (for local development) or passed as environment variables in the Cline MCP settings configuration.

What data can I access with Linear MCP Server?

You can access issues, projects, teams, comments, and rich text descriptions. Operations are limited to what the Linear API exposes through the server's tools.

Are there any known limitations?

Bulk issue updates are still in testing. Features like label management, cycle/milestone management, OAuth flow, rate limiting, and pagination are under development.