Linear MCP Server logo

Linear MCP Server

by cline

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

View on GitHub

Last updated: N/A

What is Linear MCP Server?

The Linear MCP Server is a tool that acts as a middleman between Cline and the Linear API, enabling users to manage Linear issues, projects, and teams through Cline.

How to use Linear MCP Server?

To use the server, first clone the repository and install dependencies. Then, configure authentication using a Personal Access Token. Build and start the server, and finally, integrate it with Cline by adding the server configuration to your Cline MCP settings file.

Key features of Linear MCP Server

  • Issue Management (create, update, delete, search, associate)

  • Project Management (create, get info, associate issues)

  • Team Management (get info, access states and labels)

  • Personal Access Token (PAT) authentication

  • Bulk Operations (issue creation, deletion, updates)

Use cases of Linear MCP Server

  • Automating issue creation and updates in Linear.

  • Managing Linear projects and teams through Cline.

  • Performing bulk operations on Linear issues.

  • Integrating Linear with other tools and services.

  • Streamlining Linear workflows for increased efficiency.

FAQ from Linear MCP Server

What is an MCP server?

MCP stands for Message Control Protocol. In this context, it's a server that acts as an intermediary between Cline and the Linear API.

What authentication methods are supported?

The server primarily supports Personal Access Token (PAT) authentication. OAuth flow is planned but not yet implemented.

How do I integrate the server with Cline?

You need to add the Linear MCP server configuration to your Cline MCP settings file, specifying the command, arguments, and environment variables.

What kind of issue management operations are supported?

The server supports creating, updating, deleting, searching, and associating issues with projects, as well as creating parent/child issue relationships.

What are the future development plans?

Future development includes comment functionality, complex search filters, pagination support, label management, cycle/milestone management, project template support, OAuth flow with automatic token refresh, rate limiting, detailed logging, and load testing.