← Back to directory

Linear MCP Server

Community

An MCP server for interacting with Linear's API to manage issues, projects, and teams.

GitHub source repository ↗

★ 134 Stars Category · Collaboration Popular Source revision 023ac902e0f5

35FMRS · D

Reliability

8/20

Security and permissions

5/20

Maintenance

7/20

Documentation

8/20

Setup experience

7/20

This server provides basic Linear integration, supporting issue, project, and team management. It emphasizes rich text description handling and offers batch operation capabilities. However, OAuth is not yet implemented, and some features are under development. Suitable for users using Cline and needing direct API access.

Read the FMRS scoring method →

This is a private MCP server designed for Cline to access Linear's API. It provides a set of tools for managing Linear issues, projects, and teams. It supports API Key authentication (recommended); OAuth flow is not implemented. The server implements support for Linear's rich text description field (documentContent) to ensure project descriptions are fully displayed.

Tools

create_issue

Create issues with full field support (title, description, team, project, etc.).

update_issue

Update existing issues (priority, description, etc.).

delete_issue

Delete issues (single or bulk deletion).

search_issues

Search issues with filtering.

create_comment

Read and create comments and threaded comments.

get_project

Get project information with rich text descriptions.

search_projects

Search projects with rich text descriptions.

create_project

Create projects with associated issues.

get_team

Get team information (with states and workflow details).

bulk_create_issues

Bulk create issues.

bulk_delete_issues

Bulk delete issues.

Setup

Clone the repository
Run npm install
Copy .env.example to .env
Create a personal API key in Linear settings and add it to the .env file as LINEAR_API_KEY
Run npm run build and npm start
Add the server configuration to Cline's MCP settings file (see install_config)

claude_desktop_config.json

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

Generate and validate client config

Fit and risk

Best for

Developers using Cline who need access to Linear
Teams wanting to integrate Linear issue management with AI coding assistants

Not for

Users requiring OAuth authentication (not implemented)
Users needing advanced search filtering or pagination (under development)
Non-Cline users (README focuses on Cline integration)

Required permissions

Requires a valid Linear API key (personal access token)
The API key's permissions are the same as the creating user, potentially allowing creation, update, and deletion of issues

Risks and side effects

Leaked API keys could lead to unauthorized access
Bulk operations might accidentally delete or modify many issues
Server is a private project and may have undiscovered bugs or security issues

Troubleshooting

Check that the API key is valid and not expired
Ensure `.env` is correctly configured and includes `LINEAR_API_KEY`
Verify the build succeeded: run `npm run build`
Check the path in the Cline configuration points to the correct `build/index.js`
Inspect server logs for error messages

Use cases

Manage and query Linear issues within AI assistants like Cline

Automate creation, updates, and deletion of issues

Retrieve rich text descriptions of projects

Perform bulk operations on issues

Supported clients

Claude DesktopFull support

Related MCP servers

Compare with other MCP servers