MCP Connector

Manage Linear Projects via AI

A comprehensive Linear MCP server exposing resources for every major entity, plus tools and prompt templates for project management.

Works with linear

Maintainer of this project? Claim this page to edit the listing.


90
Spark score
out of 100
Updated Mar 2025
Version 1.0.0
Models
universal

Add to Favorites

Why it matters

Empower AI assistants to fully manage your Linear projects. This connector provides comprehensive access to issues, projects, roadmaps, and more, enabling automated project management tasks.

Outcomes

What it gets done

01

Create and update Linear issues and projects

02

Link projects to initiatives and manage documents

03

Search across all Linear objects

04

Automate team and organization-level project tasks

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-linear-mcp | bash

Capabilities

Tools your agent gets

create_issue

Create new issues in Linear

update_issue

Update existing issues

add_comment

Add comments to issues

create_project

Create new projects

update_project

Update existing projects

add_issues_to_project

Add issues to projects

create_initiative

Create initiatives

link_project_to_initiative

Link projects to initiatives

+2 tools

Overview

Linear MCP Server

Exposes Linear's full data model as MCP resources (issues, teams, projects, initiatives, roadmaps, milestones, documents), plus tools for issue/project/initiative management and prompt templates for bug reports and status updates. Use when an assistant needs broad, structured Linear workspace access beyond basic issue CRUD - navigating team/project/initiative relationships or generating templated project content.

What it does

This Linear MCP server gives an AI assistant broad access to Linear's project management platform through three MCP primitives: resources, tools, and prompts. Resources cover every major Linear entity - issues, teams, projects, users, and initiatives as core resources; roadmaps, milestones, documents, integrations, and organization info as additional resources; and specialized scoped resources like a team's issues, a user's assigned issues, a project's issues, a team's workflow states/labels/cycles/members/documents, a project's documents and associated initiative, an initiative's projects, a milestone's projects, and organization-level subscription/auth-service details. Each core resource is addressable both as a collection (for example linear://issues) and by ID (linear://issues/{id}).

Tools cover issue management (creating, updating, and commenting on issues), project management (creating and updating projects, adding issues to a project), initiative management (creating initiatives, linking or unlinking projects to an initiative), and comprehensive search across Linear entities for finding issues matching specific criteria. Prompts provide reusable templates for issue-related tasks (creating new issues, bug reports, feature requests) and project-related tasks (creating new projects, planning projects with issues, and generating project status updates).

When to use - and when NOT to

Use this when an AI assistant needs deep, structured access to a Linear workspace - not just creating and searching issues, but navigating the relationships between teams, projects, initiatives, milestones, and roadmaps, or generating structured content like bug reports and status updates from a template. Its resource model is significantly broader than a minimal issue-CRUD integration, so it fits workflows that need to traverse Linear's actual data model (a team's cycles and labels, a project's linked initiative, an initiative's set of projects) rather than just single-issue operations.

Capabilities

The server supports two transports: stdio for CLI tools and direct MCP client integration, and an HTTP service using Server-Sent Events on a configurable port (3000 by default) for remote connections. It can be tested with the MCP Inspector, either over stdio or by connecting the Inspector to a running HTTP server's URL.

How to install

Setup clones the repository, installs dependencies with npm install, sets a Linear API key in a .env file, and builds with npm run build. The server then runs via npm start (stdio) or node dist/index.js http (HTTP/SSE), with npm run dev available for development with automatic reloading. For Claude Desktop, the server is added under Settings -> Advanced -> MCP Configuration, running node against the built dist/index.js with LINEAR_API_KEY passed through the env block - a claude-desktop-config.json template is provided as a starting point. Configuration is environment-variable driven: LINEAR_API_KEY is required, while SERVER_PORT (default 3000) and LOG_LEVEL (default info) are optional.

Who it's for

Teams using Linear who want an AI assistant with full visibility into their workspace's structure - issues, projects, initiatives, roadmaps, and team configuration - not just basic issue creation, plus reusable prompt templates for common project-management writing tasks like bug reports and status updates.

Source README

Linear MCP Server

A Model Context Protocol (MCP) server for Linear, providing AI assistants with access to Linear's project management capabilities.

Features

  • Resources: Access issues, projects, teams, users, roadmaps, documents, initiatives, and more
  • Tools: Create and update issues, manage projects, search, link projects to initiatives
  • Prompts: Templates for issue creation, bug reports, feature requests, and more

Setup

Prerequisites

  • Node.js 18 or later
  • A Linear API key

Installation

  1. Clone the repository:

    git clone https://github.com/yourusername/linear-mcp.git
    cd linear-mcp
    
  2. Install dependencies:

    npm install
    
  3. Create a .env file with your Linear API key:

    LINEAR_API_KEY=your_linear_api_key_here
    
  4. Build the project:

    npm run build
    

Usage

Command-line (stdio)

To run the server with stdio transport (for use with CLI tools that support MCP):

npm start

Or:

node dist/index.js stdio

HTTP Server (for remote connections)

To run the server as an HTTP service with Server-Sent Events (SSE):

node dist/index.js http

This will start an HTTP server on port 3000 (configurable via PORT environment variable).

Development Mode

To run in development mode with automatic reloading:

npm run dev

Claude Desktop Integration

To use this server with Claude Desktop:

  1. Build the project:

    npm run build
    
  2. In Claude Desktop, go to Settings → Advanced → MCP Configuration.

  3. Add the following configuration (adjust paths to match your installation):

    {
      "mcpServers": {
        "linear": {
          "command": "node",
          "args": [
            "/path/to/linear-mcp/dist/index.js"
          ],
          "env": {
            "LINEAR_API_KEY": "your_linear_api_key_here"
          }
        }
      }
    }
    
  4. Save the configuration and restart Claude Desktop.

Alternatively, you can copy the provided claude-desktop-config.json file and modify the paths to match your installation.

Resources

The server provides access to all major Linear entities as resources:

Core Resources

  • Issues: linear://issues and linear://issues/{id}
  • Teams: linear://teams and linear://teams/{id}
  • Projects: linear://projects and linear://projects/{id}
  • Users: linear://users and linear://users/{id}
  • Initiatives: linear://initiatives and linear://initiatives/{id}

Additional Resources

  • Roadmaps: linear://roadmaps and linear://roadmaps/{id}
  • Milestones: linear://milestones and linear://milestones/{id}
  • Documents: linear://documents and linear://documents/{id}
  • Integrations: linear://integrations and linear://integrations/{id}
  • Organization: linear://organization

Specialized Resources

  • linear://teams/{teamId}/issues - Issues for a specific team
  • linear://users/{userId}/issues - Issues assigned to a specific user
  • linear://projects/{projectId}/issues - Issues in a specific project
  • linear://teams/{teamId}/states - Workflow states for a team
  • linear://teams/{teamId}/labels - Labels for a team
  • linear://teams/{teamId}/cycles - Cycles for a team
  • linear://teams/{teamId}/members - Members of a team
  • linear://teams/{teamId}/documents - Documents for a team
  • linear://projects/{projectId}/documents - Documents for a project
  • linear://projects/{projectId}/initiative - Initiative associated with a project
  • linear://initiatives/{initiativeId}/projects - Projects associated with an initiative
  • linear://milestones/{milestoneId}/projects - Projects for a milestone
  • linear://organization/subscription - Organization subscription details
  • linear://organization/auth-services - Organization authentication services
  • linear://integration-services - Available integration services

Tools

The server provides tools for:

  • Issue Management

    • Creating new issues
    • Updating existing issues
    • Adding comments to issues
  • Project Management

    • Creating new projects
    • Updating existing projects
    • Adding issues to projects
  • Initiative Management

    • Creating initiatives
    • Linking projects to initiatives
    • Unlinking projects from initiatives
  • Search Capabilities

    • Comprehensive search across Linear entities
    • Finding issues with specific criteria

Prompts

The server provides prompt templates for:

  • Issue Related

    • Creating new issues
    • Creating bug reports
    • Creating feature requests
  • Project Related

    • Creating new projects
    • Planning projects with issues
    • Creating project status updates

Testing

Test with the MCP Inspector:

npx @modelcontextprotocol/inspector stdio -- npm start

Or, if running in HTTP mode, open the MCP Inspector in your browser and connect to your server's URL.

Environment Variables

  • LINEAR_API_KEY (required): Your Linear API key
  • SERVER_PORT (optional): Port for HTTP server (default: 3000)
  • LOG_LEVEL (optional): Logging level (default: info)

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.