Skip to main content
mcpFirst-partyLow risk Safety Privacy
Linear logo

Linear MCP Server for Claude

Integrate with Linear's issue tracking and project management system

HarnessClaude CodeCursorClaude Desktop

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://linear.app/docs/mcp, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/linear-mcp-server.mdx
Brand
Linear
Brand domain
linear.app
Brand asset source
brandfetch
Package URL
/downloads/mcp/linear-mcp-server.mcpb
Package SHA256
a9f6c46cfbe25cd19a67129ccf249c2f16e590b68f75597008c5192fbf9cfe20
Safety notes
Scope the Linear token to the intended workspace and review issue or project writes before changing active roadmaps.
Privacy notes
Issue text, comments, assignees, labels, project context, customer references, and workspace metadata may be sent through tool calls.
Author
Linear
Claim status
unclaimed
Last verified
2025-09-18

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

2 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

10 to clear

Platforms

3 listed

Difficulty

6/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

10 prerequisites to line up before setup. Have accounts and credentials ready first.

0/10 ready
Account & credentials4Configuration1Network & hosting2General32 minutes

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens.

2 areas
  • SafetyCredentials & tokensScope the Linear token to the intended workspace and review issue or project writes before changing active roadmaps.
  • PrivacyGeneralIssue text, comments, assignees, labels, project context, customer references, and workspace metadata may be sent through tool calls.

Safety notes

  • Scope the Linear token to the intended workspace and review issue or project writes before changing active roadmaps.

Privacy notes

  • Issue text, comments, assignees, labels, project context, customer references, and workspace metadata may be sent through tool calls.

Prerequisites

  • Linear workspace account (Member or Admin role required, not Guest)
  • OAuth credentials or Personal API Key (generate from Linear Security & access settings)
  • SSE transport support (remote MCP server at https://mcp.linear.app/sse)
  • Internet connection (remote Linear API access required)
  • Understanding of Linear API rate limits (API Key: 1,500 req/hour, 250K complexity/hour; OAuth: 1,200 req/hour, 200K complexity/hour)
  • Understanding of GraphQL query complexity limits (maximum 10,000 points per query)
  • Understanding of Linear workspace permissions and team access settings
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of project management concepts (issues, projects, cycles, teams, workflows)
  • Optional: Webhook setup for real-time updates instead of polling

Schema details

Install type
package
Reading time
1 min
Difficulty score
6
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
a9f6c46cfbe25cd19a67129ccf249c2f16e590b68f75597008c5192fbf9cfe20
Collection metadata
Estimated setup
2 minutes
Difficulty
beginner
Full copyable content
{
  "linear": {
    "url": "https://mcp.linear.app/sse",
    "transport": "sse"
  }
}

About this resource

Content

Streamline your project management and issue tracking by connecting Claude to Linear. Create and update issues, manage projects and cycles, track team velocity, query with advanced GraphQL filters, automate workflows, and receive real-time updates via webhooks—all through natural language commands. Leverage Linear's powerful API with rate limit monitoring and complexity-aware queries.

Features

  • Create and update issues with full metadata (title, description, labels, assignees, status)
  • Manage projects and cycles programmatically (create, update, track progress)
  • Track team velocity and progress metrics (sprint reports, burndown charts)
  • Query and filter issues with advanced GraphQL search (custom filters, pagination)
  • Update issue status and assignments in bulk operations
  • Manage teams and workspace settings (team creation, member management)
  • Webhook integration for real-time updates (avoid polling, receive instant notifications)
  • Advanced GraphQL queries with custom filtering and sorting (complex queries up to 10,000 points)
  • Advanced Linear issue and project management with team collaboration features, sprint planning, and workflow automation
  • Batch operations support for efficient bulk issue operations, project management, and team coordination with automatic rate limit handling and retry logic
  • Real-time project synchronization capabilities with webhook integration support for monitoring Linear events and triggering automated workflows

Use Cases

  • Create issues from bug reports or feature requests with automatic metadata population
  • Update issue status in bulk operations across multiple issues
  • Generate sprint reports and velocity metrics with custom aggregations
  • Track project progress across teams with real-time updates
  • Automate issue triage and assignment based on rules and filters
  • Query and filter issues using advanced GraphQL queries for project analysis
  • Sync Linear data with external systems via webhooks and API integration
  • Manage team workflows and workspace settings programmatically
  • Build automated project management workflows that sync external systems with Linear for real-time issue tracking and team collaboration

Installation

Claude Code

  1. claude mcp add --transport sse linear https://mcp.linear.app/sse
  2. Authenticate through OAuth when prompted (or use Personal API Key)
  3. Verify installation: claude mcp list
  4. Test connection: claude mcp status linear
  5. Verify access: Ask Claude to list your issues

Claude Desktop

  1. Open Claude Desktop configuration file (see configPath below)
  2. Add the Linear server configuration with SSE transport pointing to https://mcp.linear.app/sse
  3. Restart Claude Desktop
  4. Authenticate through OAuth when prompted (or configure Personal API Key)
  5. Verify access: Ask Claude to list your issues

Requirements

  • Linear workspace account (Member or Admin role required, not Guest)
  • OAuth credentials or Personal API Key (generate from Linear Security & access settings)
  • SSE transport support (remote MCP server at https://mcp.linear.app/sse)
  • Internet connection (remote Linear API access required)
  • Understanding of Linear API rate limits (API Key: 1,500 req/hour, 250K complexity/hour; OAuth: 1,200 req/hour, 200K complexity/hour)
  • Understanding of GraphQL query complexity limits (maximum 10,000 points per query)
  • Understanding of Linear workspace permissions and team access settings
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of project management concepts (issues, projects, cycles, teams, workflows)
  • Optional: Webhook setup for real-time updates instead of polling

Configuration

{
  "linear": {
    "url": "https://mcp.linear.app/sse",
    "transport": "sse"
  }
}

Examples

Create a new bug issue for the login problem

Common usage pattern for this MCP server

Ask Claude: "Create a new bug issue for the login problem"

Show me all issues assigned to me

Common usage pattern for this MCP server

Ask Claude: "Show me all issues assigned to me"

Update issue LIN-123 to 'In Progress'

Common usage pattern for this MCP server

Ask Claude: "Update issue LIN-123 to 'In Progress'"

List all issues in the current sprint

Common usage pattern for this MCP server

Ask Claude: "List all issues in the current sprint"

Create Issue with Labels

Create a new Linear issue with priority and labels

// Create Linear issue with labels
const issue = await linear.issues.create({
  teamId: "team-id",
  title: "Fix authentication bug",
  description: "Issue description",
  priority: 1,
  labelIds: ["label-id-1", "label-id-2"],
});

Security

  • OAuth tokens are managed securely by Linear (access tokens expire after 24 hours, refresh tokens available)
  • Permissions follow Linear workspace settings (Member or Admin role required)
  • Tokens auto-refresh as needed (for OAuth apps created after Oct 1, 2025)
  • All actions are audited in Linear (workspace activity logs)
  • Monitor rate limit headers (X-RateLimit-Requests-Remaining, X-RateLimit-Complexity-Remaining) to avoid service disruption
  • Linear API keys and personal access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • Linear OAuth access tokens should be used for third-party integrations to ensure proper access control, token lifecycle management, and automatic token refresh
  • Linear issue, project, and team IDs may expose organizational structure and development patterns - ensure Linear resource identifiers are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for Linear MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • Linear webhook configurations and payloads may contain sensitive issue data and project information - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

OAuth access token expired - 401 Unauthorized error

Access tokens expire after 24 hours. Re-authenticate to get new token with refresh token enabled (default for OAuth apps created after Oct 1, 2025). Token refreshes automatically in compliant clients. Check token expiration in response headers. For Personal API Key authentication, keys don't expire but can be revoked in Security & access settings.

Rate limit exceeded - RATELIMITED error code returned

API key auth: 1,500 requests/hour, 250K complexity points/hour. OAuth app: 1,200 requests/hour, 200K complexity points/hour. Unauthenticated: 60 req/hour, 10K complexity/hour. Monitor X-RateLimit-Requests-Remaining and X-RateLimit-Complexity-Remaining headers. Implement exponential backoff. Use webhooks instead of polling for real-time updates. Order queries by updated timestamp to fetch recent changes first. Contact Linear support for temporary limit increase if needed.

GraphQL query complexity limit exceeded - 10,000 points

Single query cannot exceed 10,000 complexity points. Reduce query depth or split into multiple smaller queries. Remove unnecessary nested fields. Use filtering to narrow data scope. Check query complexity in Linear docs. Monitor X-Complexity header in responses. Paginate large result sets to reduce complexity per query.

Insufficient workspace permissions for operation

Verify your Linear account has Member or Admin role (not Guest). Check workspace settings for user permissions. Contact workspace admin to upgrade role if needed. Verify team access permissions for specific teams. Some operations require Admin role (e.g., workspace settings, team management).

Linear MCP server authentication errors with API keys

Verify API key is valid and not expired. Check API key permissions match required operations. Ensure API key format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

Linear rate limit errors when making multiple API calls

Implement exponential backoff retry logic with jitter. Use Linear API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed issue data. Linear allows 10,000 requests per hour per API key.

Linear issue or project access denied errors

Verify API key has access to the issue or project. Check team permissions and workspace membership. Ensure API key has required scopes for target operations.

Linear MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Linear API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Source citations

Add this badge to your README

Show that Linear MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/linear-mcp-server.svg)](https://heyclau.de/entry/mcp/linear-mcp-server)

How it compares

Linear MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Source provenance).

Field

Integrate with Linear's issue tracking and project management system

Open dossier

Manage Jira tickets and Confluence documentation

Open dossier

Interact with Asana workspaces to manage projects and tasks

Open dossier

Task management and project tracking with ClickUp integration

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage verifiedPackage verifiedPackage verifiedPackage verified
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
Submitter
Install riskLow riskLow riskLow riskLow risk
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandLinear logoLinearJira logoJiraAsana logoAsanaClickUp logoClickUp
Categorymcpmcpmcpmcp
Sourcefirst-partyfirst-partyfirst-partyfirst-party
AuthorLinearAtlassianAsanahauptsacheNet
Added2025-09-182025-09-182025-09-182025-09-18
Platforms
Claude CodeCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesScope the Linear token to the intended workspace and review issue or project writes before changing active roadmaps.Scope Atlassian access and review issue or page writes because updates can notify teams and change project records.Use a least-privilege Asana token and test task or project writes in a non-critical workspace before connecting production workflows.Scope the ClickUp API key to the intended team and review task, status, or project mutations before using it on active workspaces.
Privacy notesIssue text, comments, assignees, labels, project context, customer references, and workspace metadata may be sent through tool calls.Jira tickets, Confluence pages, comments, attachments, user metadata, and organization details may be sent through tool calls.Asana task text, project metadata, comments, assignees, due dates, and workspace details may be sent through model context.Tasks, comments, custom fields, assignees, due dates, and workspace metadata may be exposed through tool calls.
Prerequisites
  • Linear workspace account (Member or Admin role required, not Guest)
  • OAuth credentials or Personal API Key (generate from Linear Security & access settings)
  • SSE transport support (remote MCP server at https://mcp.linear.app/sse)
  • Internet connection (remote Linear API access required)
  • Atlassian account (Jira Cloud or self-hosted Jira instance access)
  • OAuth credentials or API token (Jira Cloud: email + API token from account settings; self-hosted: Personal Access Token or OAuth)
  • HTTP/SSE transport support (remote MCP server at https://mcp.atlassian.com/v1/sse)
  • Internet connection (remote Atlassian API access required)
  • OAuth 2.0 authentication (required for MCP server via SSE transport)
  • Asana account with access to at least one workspace
  • Workspace membership with Member role or higher (Guest role insufficient for task creation)
  • Internet connection for accessing Asana API (https://app.asana.com)
  • ClickUp account with workspace access
  • ClickUp Personal API Token from https://app.clickup.com/settings/apps
  • ClickUp Team ID (found in ClickUp workspace settings)
  • Node.js and npm/npx available for running the @hauptsache.net/clickup-mcp package
Install
claude mcp list && claude mcp status linear
claude mcp list && claude mcp status jira
claude mcp list && claude mcp status asana
claude mcp add clickup --env CLICKUP_API_KEY=YOUR_KEY --env CLICKUP_TEAM_ID=YOUR_TEAM_ID -- npx -y @hauptsache.net/clickup-mcp && claude mcp list
Config
{
  "mcpServers": {
    "linear": {
      "url": "https://mcp.linear.app/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "atlassian": {
      "url": "https://mcp.atlassian.com/v1/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "asana": {
      "url": "https://mcp.asana.com/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "clickup": {
      "env": {
        "CLICKUP_API_KEY": "${CLICKUP_API_KEY}",
        "CLICKUP_TEAM_ID": "${CLICKUP_TEAM_ID}"
      },
      "args": [
        "-y",
        "@hauptsache.net/clickup-mcp"
      ],
      "command": "npx",
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.