npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@odgrim/linear-mcp

v0.0.2

Published

fork of cline linear-mcp, fixed for api keys

Readme

Linear MCP Server

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

Setup Guide

1. Environment Setup

  1. Clone the repository
  2. Install dependencies:
    npm install
  3. Copy .env.example to .env:
    cp .env.example .env

2. Authentication

The server supports two authentication methods:

Personal Access Token via Environment Variable (Recommended for Dev/Single Users)

  1. Go to Linear: Settings > API > OAuth application > "Cline MCP"
  2. Under "Developer Token", click "Create & copy token"
  3. Select "Application"
  4. Add the token to your .env file:
    LINEAR_ACCESS_TOKEN=your_personal_access_token

This method is simple and suitable for testing and development environments.

Optionally, you can use an API key here instead.

OAuth Flow (Recommended for production)

  1. Create an OAuth application at https://linear.app/settings/api/applications
  2. Configure OAuth environment variables in .env:
    LINEAR_CLIENT_ID=your_oauth_client_id
    LINEAR_CLIENT_SECRET=your_oauth_client_secret
    LINEAR_REDIRECT_URI=http://localhost:3000/callback
  3. Use the linear_auth tool to initiate the OAuth flow:
    {
      "clientId": "your_client_id",
      "clientSecret": "your_client_secret",
      "redirectUri": "your_redirect_uri"
    }
  4. Follow the authorization URL to grant access
  5. Use the linear_auth_callback tool with the authorization code:
    {
      "code": "authorization_code_from_redirect"
    }

This method is more secure and recommended for production environments and multi-user scenarios.

3. Running the Server

  1. Build the server:
    npm run build
  2. Start the server:
    npm start

4. Cline Integration

  1. Open your Cline MCP settings file:

    • macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
    • Windows: %APPDATA%/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
    • Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
  2. Add the Linear MCP server configuration:

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

Available Actions

The server currently supports the following operations:

Authentication

  • ✅ Personal Access Token (PAT) authentication via environment variable
  • ✅ OAuth flow authentication
  • ✅ Secure token storage

Issue Management

  • ✅ Create issues with full field support (title, description, team, project, etc.)
  • ✅ Update existing issues (priority, description, etc.)
  • ✅ Delete issues (single or bulk deletion)
  • ✅ Search issues with filtering
  • ✅ Associate issues with projects
  • ✅ Create parent/child issue relationships

Project Management

  • ✅ Create projects with associated issues
  • ✅ Get project information
  • ✅ Associate issues with projects

Team Management

  • ✅ Get team information (with states and workflow details)
  • ✅ Access team states and labels

Batch Operations

  • ✅ Bulk issue creation
  • ✅ Bulk issue deletion

Bulk Updates (In Testing)

  • 🚧 Bulk issue updates (parallel processing implemented, needs testing)

Features in Development

The following features are currently being worked on:

Issue Management

  • 🚧 Comment functionality (add/edit comments, threading)
  • 🚧 Complex search filters
  • 🚧 Pagination support for large result sets

Metadata Operations

  • 🚧 Label management (create/update/assign)
  • 🚧 Cycle/milestone management

Project Management

  • 🚧 Project template support
  • 🚧 Advanced project operations

Authentication

  • 🚧 OAuth flow with automatic token refresh

Performance & Security

  • 🚧 Rate limiting
  • 🚧 Detailed logging
  • 🚧 Load testing and optimization

Development

# Install dependencies
npm install

# Run tests
npm test

# Run integration tests (requires LINEAR_ACCESS_TOKEN)
npm run test:integration

# Build the server
npm run build

# Start the server
npm start

Integration Testing

Integration tests verify that authentication and API calls work correctly:

  1. Set up authentication (PAT recommended for testing)
  2. Run integration tests:
    npm run test:integration

For OAuth testing:

  1. Configure OAuth credentials in .env
  2. Remove .skip from OAuth tests in src/__tests__/auth.integration.test.ts
  3. Run integration tests