Skip to main content
Glama
Linear MCP Server

Linear MCP Server

by wkoutre

Linear MCP Server

A Model Context Protocol (MCP) server implementation for the Linear GraphQL API that enables AI assistants to interact with Linear project management systems.

Linear MCP Server npm version Smithery

Features

  • Access to Linear's GraphQL API through MCP tools

  • Authentication via Linear API key

  • Retrieve and modify data related to users, teams, projects, and issues

  • Create, update and comment on issues

  • Add and remove labels

  • Create projects

  • Comprehensive documentation of available tools

Related MCP server: Linear MCP Server

Installation

To install Linear MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @emmett.deen/linear-mcp-server --client claude

Manual Configuration

After installation, add the following to your MCP settings file:

{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": ["-y", "@emmett.deen/linear-mcp-server"],
      "env": {
        "LINEAR_API_KEY": "your_linear_api_key_here"
      }
    }
  }
}

Client-Specific Configuration Locations

  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Claude VSCode Extension: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

  • GoMCP: ~/.config/gomcp/config.yaml

Manual Installation

  1. Clone the repository

git clone https://github.com/yourusername/Linear-MCP-Server.git
cd Linear-MCP-Server
  1. Install dependencies

npm install
  1. Build the project

npm run build
  1. Create a .env file with your Linear API token

LINEAR_API_KEY=your_linear_api_key_here
  1. Start the server

npm start

Available Tools

See TOOLS.md for a complete list of available tools and planned features.

Overview

Linear-MCP-Server bridges the gap between Claude (AI assistant) and Linear (project management tool) by implementing the MCP protocol. This allows Claude to:

  • Retrieve issues, projects, teams, and other data from Linear

  • Create and update issues

  • Change issue status

  • Assign issues to team members

  • Add comments

  • Create projects and teams

The server uses Linear's GraphQL API and authenticates via user tokens (not OAuth) for simplicity.

Getting Started

Prerequisites

  • Node.js (v18+)

  • NPM or Yarn

  • Linear API token

Installation

# Install globally
npm install -g @emmett.deen/linear-mcp-server

# Or clone and install locally
git clone https://github.com/yourusername/Linear-MCP-Server.git
cd Linear-MCP-Server
npm install
npm link  # Makes the package available globally

Running the Server

Run the server with your Linear API token:

linear-mcp-server --token YOUR_LINEAR_API_TOKEN

Or set the token in your environment and run without arguments:

export LINEAR_API_TOKEN=YOUR_LINEAR_API_TOKEN
linear-mcp-server

Using with Claude Desktop

To use this MCP server with Claude Desktop:

  1. Enable Developer Mode in Claude Desktop (from the menu bar)

  2. Go to Settings > Developer options

  3. Click "Add Server"

  4. Configure with the following settings:

    • Name: Linear MCP Server

    • Type: Local Process

    • Command: linear-mcp-server

    • Arguments: --token YOUR_LINEAR_API_TOKEN

Alternatively, manually edit the config file:

{
  "mcp": {
    "servers": [
      {
        "name": "Linear MCP Server",
        "transport": {
          "type": "stdio",
          "command": "linear-mcp-server",
          "args": ["--token", "YOUR_LINEAR_API_TOKEN"]
        }
      }
    ]
  }
}
  1. Save the config

  2. Restart Claude Desktop (quit completely and reopen)

  3. You should now see Linear MCP Server available as a tool in Claude

Example Claude Prompts

Once connected to Claude Desktop, you can use prompts like:

  • "Show me all my Linear issues"

  • "Create a new issue titled 'Fix login bug' in the Frontend team"

  • "Change the status of issue FE-123 to 'In Progress'"

  • "Assign issue BE-456 to John Smith"

  • "Add a comment to issue UI-789: 'This needs to be fixed by Friday'"

Development

To develop locally:

# Clone the repository
git clone https://github.com/yourusername/Linear-MCP-Server.git
cd Linear-MCP-Server

# Install dependencies
npm install

# Run in development mode
npm run dev -- --token YOUR_LINEAR_API_TOKEN

Extending the Server

To add new tools to the server:

  1. Follow the implementation guide in the TOOLS.md document

  2. Make sure to follow the established code structure in the src/ directory

  3. Update the documentation to reflect your changes

Developing and Contributing

Setup Development Environment

  1. Clone the repository

git clone https://github.com/yourusername/Linear-MCP-Server.git
cd Linear-MCP-Server
  1. Install dependencies

npm install
  1. Start in development mode

npm run dev

Publishing to npm

To publish this package to npm:

  1. Update the version in package.json

npm version patch  # or minor, or major
  1. Build the project

npm run build
  1. Make sure you've already logged in to npm

npm login
  1. Publish to npm

npm publish --access public
  1. For Smithery registry, you'll need to work with the Smithery team to get your server listed in their catalog.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Available Tools

32 tools
linear_addIssueLabelB

Add a label to an issue in Linear

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

linear_addIssueToCycleC

Add an issue to a cycle

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

linear_addIssueToProjectC

Add an existing issue to a project

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

linear_archiveIssueC

Archive an issue

Inputs: issueId (required).

linear_assignIssueB

Assign an issue to a user

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

linear_convertIssueToSubtaskC

Convert an issue to a subtask

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

linear_createCommentC

Add a comment to an issue in Linear

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

linear_createIssueC

Create a new issue in Linear

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

linear_createIssueRelationA

Create relations between issues (blocks, is blocked by, etc.)

Inputs: issueId (required), relatedIssueId (required), type (required).

linear_createProjectC

Create a new project in Linear

Inputs: name (required), teamIds (required), description, state.

linear_duplicateIssueC

Duplicate an issue

Inputs: issueId (required).

linear_getActiveCycleB

Get the currently active cycle for a team

Inputs: teamId (required).

linear_getCommentsC

Get all comments for an issue

Inputs: issueId (required), limit.

linear_getCyclesC

Get a list of all cycles

Inputs: teamId, limit.

linear_getIssueByIdA

Get a specific issue by ID or identifier (e.g., ABC-123)

Inputs: id (required).

linear_getIssueHistoryB

Get the history of changes made to an issue

Inputs: issueId (required), limit.

linear_getIssuesC

Get a list of recent issues from Linear

Inputs: limit.

linear_getLabelsB

Get a list of issue labels from Linear

Inputs: no named parameters.

linear_getOrganizationA

Get information about the current Linear organization

Inputs: no named parameters.

linear_getProjectIssuesB

Get all issues associated with a project

Inputs: projectId (required), limit.

linear_getProjectsB

Get a list of projects from Linear

Inputs: no named parameters.

linear_getTeamsB

Get a list of teams from Linear

Inputs: no named parameters.

linear_getUsersA

Get a list of users in the Linear organization

Inputs: no named parameters.

linear_getViewerA

Get information about the currently authenticated user

Inputs: no named parameters.

linear_getWorkflowStatesB

Get workflow states for a team

Inputs: teamId (required), includeArchived.

linear_removeIssueLabelC

Remove a label from an issue in Linear

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

linear_searchIssuesB

Search for issues with various filters

Inputs: query, teamId, assigneeId, projectId, +2 more.

linear_setIssuePriorityC

Set the priority of an issue

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

linear_subscribeToIssueC

Subscribe to issue updates

Inputs: issueId (required).

linear_transferIssueB

Transfer an issue to another team

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

linear_updateIssueC

Update an existing issue in Linear

Inputs: id (required), title, description, stateId, +13 more.

linear_updateProjectC

Update an existing project in Linear

Inputs: id (required), name, description, state.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 32 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions in Linear, such as linear_addIssueLabel vs. linear_removeIssueLabel or linear_getIssueById vs. linear_searchIssues. There is no ambiguity or overlap that would cause misselection, as each tool name precisely indicates its function.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with the 'linear_' prefix, such as linear_createIssue, linear_getIssues, and linear_updateIssue. The naming is uniform throughout, using snake_case and clear action verbs, making it highly predictable and readable.

    Tool Count3/5

    With 32 tools, the count is borderline high for a project management server, as it may feel heavy and complex for agents to navigate. While it covers many operations, a more streamlined set of 15-25 tools might be more appropriate for the scope without sacrificing functionality.

    Completeness5/5

    The tool surface provides comprehensive CRUD and lifecycle coverage for Linear's domain, including issue management (create, update, archive, duplicate), project handling, user and team operations, and advanced features like relations and subscriptions. There are no obvious gaps, and agents can perform full workflows without dead ends.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables comprehensive issue tracking and project management through Linear's GraphQL API. Supports creating and managing issues, organizing projects and sprints, team collaboration, and roadmap planning for modern development workflows.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to interact with Linear's issue tracking system, including creating, updating, searching issues, adding comments, and accessing resources via the Linear API.
      MIT