Skip to main content
Glama
linear-mcp
by gerbal

Linear MCP Server

Note: This is a custom implementation. For the official Cline Linear MCP server, see cline/linear-mcp.

A Model Context Protocol (MCP) server that provides tools for interacting with Linear's API, enabling AI agents to manage issues, projects, teams, and more programmatically.

Installation

Prerequisites

  • Node.js (v16 or higher)

  • A Linear account with API access

  • Linear API key with appropriate permissions (get from Linear's Developer Settings)

Related MCP server: Linear MCP Server

Usage

Quick Start

You need to provide your Linear API key to the server.

Option 1: Command Line Argument

LINEAR_API_KEY=your-api-key npx @gmclend/linear-mcp

Option 2: Environment Variable

export LINEAR_API_KEY=your-api-key
# Then run the server
npx @gmclend/linear-mcp

Client Configuration

Configure your MCP client (e.g., in its settings file) to connect to this server:

{
  "mcpServers": {
    "linear-mcp": {
      "command": "npx",
      "args": ["-y", "@gmclend/linear-mcp"],
      "env": {
        "LINEAR_API_KEY": "your-api-key-here",
        // Optional: Enable read-only mode (see below)
        "LINEAR_MCP_READ_ONLY": "false" 
      }
    }
  }
}

Read-Only Mode

Run the server in read-only mode to prevent accidental modifications and limit the available tools (useful in restricted environments). Set the LINEAR_MCP_READ_ONLY environment variable:

LINEAR_MCP_READ_ONLY=true LINEAR_API_KEY=your-api-key npx @gmclend/linear-mcp

Features

This server provides comprehensive tools for managing various Linear entities:

  • Issue Management: Create, list (with filters), update, and search issues.

  • Comment Management: Create, view, update, and delete comments on issues.

  • Label Management: List, create, and update team labels.

  • Team Management: List teams and view team details.

  • Project Management: List projects (with filters) and view project details.

  • Cycle Management: List, create, and update team cycles.

  • Document Management: List, create, and update project documents.

  • User Management: List users, get user details, and get info about the authenticated user.

  • Roadmap/Initiative Management: List roadmaps/initiatives and get details.

Available Tools

All tools are defined in src/tools/definitions.ts.

Read-Only Tools

(Available in both standard and read-only modes)

  • list_issues: List issues with optional filters (team, assignee, status, priority, etc.).

  • search_issues: Search issues using query text.

  • get_issue: Get detailed information about a specific issue.

  • get_comment: Get a specific comment.

  • list_labels: List all labels in a team.

  • get_label: Get label details.

  • list_teams: List all teams in the workspace.

  • get_team: Get team details.

  • list_projects: List all projects with optional filters (see Project Filters section).

  • get_project: Get project details.

  • list_cycles: List all cycles in a team.

  • get_cycle: Get cycle details.

  • list_documents: List all documents, optionally filtered by team.

  • get_document: Get document details.

  • list_users: List all users in the workspace.

  • get_user: Get detailed information about a specific user.

  • me: Get information about the authenticated user.

  • list_roadmaps: List all roadmaps.

  • get_roadmap: Get roadmap details.

  • get_initiative: Get detailed information about a specific initiative.

Write Tools

(Only available when LINEAR_MCP_READ_ONLY is not true)

  • create_issue: Create a new issue.

  • update_issue: Update an existing issue (title, description, status, assignee, priority, labels).

  • create_comment: Create a comment on an issue.

  • update_comment: Update an existing comment.

  • delete_comment: Delete a comment.

  • create_label: Create a new label.

  • update_label: Update an existing label.

  • create_cycle: Create a new cycle.

  • update_cycle: Update an existing cycle.

  • create_document: Create a new document associated with a project.

  • update_document: Update an existing document.

Filters and Pagination

Many list_* tools support filtering and pagination.

Project Filters (list_projects)

The list_projects command accepts the following filter parameters:

Filter

Description

Example

first

Max results (default: 50)

{"first": 10}

after

Cursor for forward pagination

{"after": "cursor_string"}

teamId

Filter by team ID

{"teamId": "team-uuid"}

id

Filter by specific project ID(s)

{"id": ["proj-uuid"]}

name

Filter by project name (contains)

{"name": "Refactor"}

state

Filter by project state

{"state": "started"}

health

Filter by project health

{"health": "onTrack"}

priority

Filter by priority (0-4)

{"priority": 3}

createdAfter

Filter by creation date (ISO 8601)

{"createdAfter": "2023-01-01"}

createdBefore

Filter by creation date (ISO 8601)

{"createdBefore": "2024-01-01"}

updatedAfter

Filter by update date (ISO 8601)

{"updatedAfter": "2023-06-01"}

updatedBefore

Filter by update date (ISO 8601)

{"updatedBefore": "2024-01-01"}

orderBy

Sort results by field

{"orderBy": "createdAt"}

Example Response (list_projects):

{
  "projects": [
    {
      "id": "project-id",
      "name": "Project Name",
      // ... other fields
      "teams": [ { "id": "team-id", "name": "Team Name", "key": "TEAM" } ]
    }
  ],
  "pagination": {
    "hasNextPage": true,
    "endCursor": "cursor-for-next-page"
  }
}

Initiative Pagination (list_initiatives)

The list_initiatives tool supports pagination:

  • first: Number of items from the beginning (default: 50).

  • last: Number of items from the end.

  • after: Cursor for forward pagination.

  • before: Cursor for backward pagination.

Example Response (list_initiatives):

{
  "initiatives": [ /* ... initiative data ... */ ],
  "pagination": {
    "hasNextPage": true,
    "hasPreviousPage": false,
    "startCursor": "cursor-for-first-item",
    "endCursor": "cursor-for-last-item"
  }
}

Development

Setup

  1. Clone the repository: git clone [repository-url] && cd linear-mcp

  2. Install dependencies: npm install

  3. Build the project: npm run build

Running with Inspector

For local development and debugging with a web UI:

npm run inspector

Open http://localhost:6274 in your browser.

Auto-Rebuild

For development with auto-rebuild on file changes:

npm run watch

Technical Details

  • Built with TypeScript, Linear SDK (@linear/sdk), and MCP SDK (@modelcontextprotocol/sdk).

  • Communicates via stdio using the Model Context Protocol.

  • Includes basic error handling for API keys, parameters, and Linear API issues.

License

MIT

Available Tools

31 tools
create_commentB

Create a new comment on an issue

Inputs: issueId (required), body (required).

create_cycleC

Create a new cycle for a team

Inputs: teamId (required), name (required), startDate (required), endDate (required), +1 more.

create_documentC

Create a new document

Inputs: title (required), content (required), projectId (required).

create_issueC

Create a new issue in Linear

Inputs: title (required), teamId (required), description, assigneeId, +2 more.

create_labelB

Create a new label in a team

Inputs: teamId (required), name (required), color, description.

delete_commentB

Delete a comment

Inputs: commentId (required).

get_commentC

Get a specific comment

Inputs: commentId (required).

get_cycleC

Get cycle details

Inputs: cycleId (required).

get_documentC

Get document details

Inputs: documentId (required).

get_initiativeB

Get detailed information about a specific initiative

Inputs: initiativeId (required).

get_issueB

Get detailed information about a specific issue

Inputs: issueId (required).

get_labelC

Get label details

Inputs: labelId (required).

get_projectC

Get project details

Inputs: projectId (required).

get_roadmapC

Get roadmap details

Inputs: roadmapId (required).

get_teamC

Get team details

Inputs: teamId (required).

get_userA

Get detailed information about a specific user

Inputs: userId (required).

list_cyclesC

List all cycles in a team

Inputs: teamId, first.

list_documentsC

List all documents

Inputs: teamId, first.

list_issuesC

List issues with optional filters

Inputs: teamId, assigneeId, status, projectId, +6 more.

list_labelsB

List all labels in a team

Inputs: teamId, first.

list_projectsC

List all projects

Inputs: teamId, first.

list_roadmapsC

List all roadmaps

Inputs: first.

list_teamsA

List all teams in the workspace

Inputs: no named parameters.

list_usersB

List all users in the workspace

Inputs: first.

meA

Get information about the authenticated user

Inputs: no named parameters.

search_issuesC

Search for issues using query text

Inputs: query (required), first.

update_commentB

Update an existing comment

Inputs: commentId (required), body (required).

update_cycleC

Update an existing cycle

Inputs: cycleId (required), name, description, startDate, +1 more.

update_documentB

Update an existing document

Inputs: documentId (required), title, content.

update_issueC

Update an existing issue

Inputs: issueId (required), title, description, status, +3 more.

update_labelB

Update an existing label

Inputs: labelId (required), name, color, description.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (e.g., create_comment, get_issue), and there is no overlap in purpose. The 'me' tool is unique and clear.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., list_issues, create_cycle). The only outlier is 'me', which is a standard convention for user info.

    Tool Count2/5

    With 31 tools, the server exceeds the recommended range of 3-15. While the tools cover many entities, the count feels heavy for a single MCP server.

    Completeness3/5

    The server provides create, get, list, and update for most resources, but notably lacks delete operations for issues, cycles, documents, and projects. This is a significant gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server implementation that enables AI assistants to interact with Linear project management systems, allowing them to create, retrieve, and modify data related to issues, projects, teams, and users.
      21 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Linear's issue tracking system through a standardized Model Context Protocol interface, allowing users to create, update, search, and manage issues, projects, and comments via natural language.
      317 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to interact with Linear for issue tracking and project management through the Model Context Protocol, supporting capabilities like creating issues, searching, managing sprints, and bulk updating statuses.
      5
      -