Skip to main content

​
Linear Server

​
Overview

The Linear server provides comprehensive project management and issue tracking capabilities. Built by Linear, this server enables AI assistants to manage issues, coordinate projects, track sprints, and streamline development workflows.

​
Getting Started

1

Connect to Linear

Add the Linear server to your Nexus environment through the server directory.
2

Authenticate with Linear

Connect your Linear workspace using OAuth to access your teams and projects.
3

Test Connection

Start with get user to verify authentication and list teams to see your workspace structure.

​
What You Can Do

Issue Management

Create, update, search, and track issues across teams and projects

Project Coordination

Manage projects, assign leads, set timelines, and track progress

Team Organization

Coordinate teams, workflows, and sprint cycles for efficient delivery

Workflow Automation

Automate issue creation, updates, and status transitions based on development events

​
Use Cases

  • Bug Reporting: Create detailed bug reports with descriptions, priorities, and assignments
  • Feature Requests: Track feature development from concept to completion
  • Task Management: Organize development tasks with estimates and deadlines
  • Status Tracking: Monitor issue progress through customizable workflow states
  • Project Setup: Create projects with timelines, leads, and team assignments
  • Sprint Planning: Organize work into cycles with clear start and end dates
  • Progress Monitoring: Track project completion and identify blockers
  • Resource Allocation: Balance workload across team members and projects
  • Cross-team Coordination: Manage dependencies between different teams
  • Communication: Add comments and updates to issues for clear communication
  • Assignment Management: Distribute work based on expertise and availability
  • Workflow Standardization: Ensure consistent processes across teams
  • Code-to-Issue Linking: Connect code changes to specific Linear issues
  • Automated Updates: Update issue status based on Git commits and deployments
  • Release Planning: Organize issues into releases and track completion
  • Quality Assurance: Track testing, reviews, and deployment status

​
Available Tools (26)

Essential tools for understanding workspace structure and team organization.Workspace Discovery
Get information about the authenticated Linear user and workspace access
List all teams in the workspace with optional archived team inclusion
  • Parameters: includeArchived (boolean, default: false)
List all users in the workspace with activity status
  • Parameters: includeInactive (boolean, default: false)
Team IDs: Required for most operations - get them via list_teams first.
Core functionality for creating, updating, and managing Linear issues.Issue Lifecycle Management
Advanced issue search with multiple filter options
  • Filters: query, teamId, projectId, assigneeId, state, limit (1-100)
  • States: backlog, todo, in_progress, done, canceled
Get detailed information about specific issues
  • Input: Issue ID or issue number (e.g., ‘ENG-123’)
Create new issues with full metadata support
  • Required: title, teamId
  • Optional: description, projectId, assigneeId, priority (0-4), labelIds, estimate
Update existing issues with flexible field modifications
  • Updatable: title, description, stateId, assigneeId, priority, labelIds, estimate
Add markdown-formatted comments to issues for collaboration
  • Parameters: issueId (required), body (markdown format)
Priority Levels: 0=No priority, 1=Urgent, 2=High, 3=Normal, 4=Low
Tools for organizing work into projects and tracking progress.
List projects with team and archive filtering
  • Parameters: teamId (optional), includeArchived (boolean, default: false)
Create new projects with timeline and team assignments
  • Required: name, teamIds (array)
  • Optional: description, leadId, targetDate, startDate (YYYY-MM-DD)
List sprint cycles for agile development
  • Parameters: teamId (required), includeCompleted (boolean, default: false)
Date Format: Use ISO date format (YYYY-MM-DD) for startDate and targetDate parameters.
Tools for managing workflow states, labels, and team configuration.
Get workflow states and transitions for specific teams
  • Parameters: teamId (required)
  • Use Cases: Understand available states for issue updates
List available labels for categorizing and organizing issues
  • Parameters: teamId (optional filter)
  • Use Cases: Get label IDs for issue creation and updates
Always use list_workflows to get valid stateIds before updating issue states.

​
Configuration Requirements

​
Authentication Setup

The Linear server uses OAuth2 authentication with Linear’s API:
  • Read Access: View issues, projects, teams, and user data
  • Write Access: Create and update issues, projects, and comments
  • Workspace Access: Access to all teams and projects in your workspace
  • Team Member: Must be a member of teams you want to manage
  • Project Access: View and edit permissions for relevant projects
  • Issue Management: Create, update, and comment permissions
  • User Directory: Access to workspace user list for assignments

​
Best Practices

​
Issue Management Workflow

  1. Team Discovery: Use list_teams to understand workspace structure
  2. Issue Creation: Use create_issue with appropriate team, priority, and labels
  3. Progress Tracking: Use search_issues with state filters to monitor progress
  4. Status Updates: Use update_issue to move issues through workflow states
  5. Communication: Use add_comment for updates and collaboration

​
Project Planning Best Practices

  1. Project Setup: Use create_project with clear timelines and team assignments
  2. Sprint Organization: Use list_cycles to plan work in iterations
  3. Workload Distribution: Balance assignments using list_users and search filters
  4. Progress Monitoring: Track project completion with filtered issue searches

​
Workflow Optimization

  1. State Management: Use list_workflows to understand available transitions
  2. Label Strategy: Use list_labels to maintain consistent categorization
  3. Automation: Create issues automatically based on errors, deployments, or events
  4. Integration: Link issues to code commits, pull requests, and deployments

​
Team Coordination

  1. Assignment Strategy: Assign issues based on expertise and current workload
  2. Priority Management: Use priority levels consistently across teams
  3. Communication: Keep issue comments updated with progress and blockers
  4. Cross-team Dependencies: Use projects to coordinate work between teams
Always verify team IDs, user IDs, and state IDs using the list tools before creating or updating issues.
Pro Tip: Use descriptive issue titles and markdown-formatted descriptions for better searchability and team communication.