M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
L

Linear MCP Server

Community
An MCP server for interacting with Linear's API to manage issues, projects, and teams.
How to install ↓ Compare GitHub source repository ↗
Category
Collaboration #52 of 55
Stars
★ 135 Popular
Transport
stdio (local process)
Runtime
Node.js
Credentials
API key / credential required
Last commit
⚠
Tools
11
35FMRS · D

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.

Strongest · Documentation 8/20 Weakest · Security and permissions 5/20

Reliability
8/20
Security and permissions
5/20
Maintenance
7/20
Documentation
8/20
Setup experience
7/20
Why each score
Reliability 8/20
Rationale: Source files and configuration indicate a structured server with build (npm run build) and test (npm test) scripts. However, there is no verifiable execution evidence such as CI workflows or committed tests covering key paths, and the README mentions tests that are not present in the repository. Also, OAuth flow is documented but not implemented, causing a discrepancy. Thus, based on static review only, score is limited below 12.
Security and permissions 5/20
Score 5: API key handling and env vars are used, and delete operations appear to require user confirmation. However, data flow (tool calls to external API) is not disclosed, and delete operations lack explicit confirmation/cancellation details. The install example contains no real tokens, but .env.example may be missing. Source cannot be verified for security implementations, so points deducted for insufficient evidence.
Maintenance 7/20
Repository has recent commits and active issue tracking, but no license, no version tags, and no clear maintainer. In-development features in README suggest activity, but lack of security response channel and release process prevents full marks.
Documentation 8/20
README provides detailed installation, authentication, and tool lists, with in-development features and tests. However, it lacks detailed tool parameters, limitations, troubleshooting, and cost considerations. Docs may be outdated (OAuth not implemented). Points deducted for missing layered documentation and reviewable evidence.
Setup experience 7/20
Setup steps are clear: clone, npm install, copy .env, build, start. Cline client integration example is provided. But configuration is manual and requires build step, no out-of-box solution like Docker. Since not executed, score capped at 15 per static guidance.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

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

Setup

Before you start

Runtime：Node.js

LINEAR_API_KEY requiredsecret Linear personal API key, created under Settings > Security & access > Personal API keys.
LINEAR_CLIENT_SECRET optionalsecret OAuth application client secret, obtained together with LINEAR_CLIENT_ID (OAuth flow not implemented).
Other optional settings (2)
LINEAR_CLIENT_ID optional OAuth application client ID from https://linear.app/settings/api/applications (OAuth flow not implemented).
LINEAR_REDIRECT_URI optional OAuth callback URL, e.g. http://localhost:3000/callback (OAuth flow not implemented).
  1. Clone the repository
  2. Run npm install
  3. Copy .env.example to .env
  4. Create a personal API key in Linear settings and add it to the .env file as LINEAR_API_KEY
  5. Run npm run build and npm start
  6. 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": []
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

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

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add linear -e LINEAR_API_KEY=your_personal_access_token -- node /path/to/linear-mcp/build/index.js

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the server to your Cline MCP settings and restarting, check that Linear tools such as create_issue and search_issues appear in the client's tool list; calling get_team also proves the API key works.

Troubleshooting

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

Things to try

Once connected, you can ask your AI assistant things like:

  • Create a Linear issue titled 'Fix login page bug' and associate it with my frontend project
  • Search Linear for all unfinished high-priority issues
  • Show me the details of the 'Mobile' project, including its description and related issues
  • Mark this issue as done and add a comment explaining why

Tools 11

create_issue writes
Create issues with full field support (title, description, team, project, etc.).
update_issue writes
Update existing issues (priority, description, etc.).
delete_issue destructive
Delete issues (single or bulk deletion).
search_issues read-only
Search issues with filtering.
create_comment writes
Read and create comments and threaded comments.
get_project read-only
Get project information with rich text descriptions.
search_projects read-only
Search projects with rich text descriptions.
create_project writes
Create projects with associated issues.
Show 3 more tools
get_team read-only
Get team information (with states and workflow details).
bulk_create_issues writes
Bulk create issues.
bulk_delete_issues destructive
Bulk delete issues.

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 Desktop

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Compare with other MCP servers

Source revision 023ac902e0f5 Data synced 2026-10-19 Read the FMRS scoring method