Install command
Provided
Integrate with Linear's issue tracking and project management system
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Provided
Copy snippet
Provided
Prerequisites
10 to clear
Platforms
3 listed
Difficulty
6/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
10 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens.
{
"linear": {
"url": "https://mcp.linear.app/sse",
"transport": "sse"
}
}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.
{
"linear": {
"url": "https://mcp.linear.app/sse",
"transport": "sse"
}
}
Common usage pattern for this MCP server
Ask Claude: "Create a new bug issue for the login problem"
Common usage pattern for this MCP server
Ask Claude: "Show me all issues assigned to me"
Common usage pattern for this MCP server
Ask Claude: "Update issue LIN-123 to 'In Progress'"
Common usage pattern for this MCP server
Ask Claude: "List all issues in the current sprint"
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"],
});
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.
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.
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.
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).
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.
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.
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.
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.
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 status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package verified | Package verified | Package verified | Package verified |
| Source provenanceDiffers | Source-backed | No submission link | No submission link | No submission link |
| Submitter | — | — | — | — |
| Install risk | Low risk | Low risk | Low risk | Low risk |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | mcp | mcp | mcp | mcp |
| Source | first-party | first-party | first-party | first-party |
| Author | Linear | Atlassian | Asana | hauptsacheNet |
| Added | 2025-09-18 | 2025-09-18 | 2025-09-18 | 2025-09-18 |
| Platforms | Claude CodeCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Scope 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 notes | ✓Issue 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 |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.