From linear
Manages Linear issues, projects, and teams using MCP tools, linear CLI, and GraphQL API. Create, update, query issues; handle labels, status, references, and backlogs.
npx claudepluginhub bendrucker/claude --plugin linearThis skill is limited to using the following tools:
Tools and workflows for managing issues, projects, and teams in Linear.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Tools and workflows for managing issues, projects, and teams in Linear.
Choose the right tool for the task:
linear api CLI - Use for complex queries, bulk operations, or anything not supported by MCP toolsWhen writing text that references other issues (descriptions, comments, updates), never use bare identifiers like ENG-123. Linear auto-renders issue URLs as inline preview components, so use the full URL:
https://linear.app/workspace/issue/ENG-123 (renders as an inline preview)[the auth bug](https://linear.app/workspace/issue/ENG-123) (when linking specific words is more natural)Both MCP tools and GraphQL queries return a url field on issues. Always include url when querying issues you may reference in written content.
When creating issues, set the appropriate status based on assignment:
assignee: "me"): Set state: "Todo"state: "Backlog"Example:
// Issue for myself
await linear.create_issue({
team: "ENG",
title: "Fix authentication bug",
assignee: "me",
state: "Todo"
})
// Unassigned issue
await linear.create_issue({
team: "ENG",
title: "Research API performance",
state: "Backlog"
})
Use assignee: "me" to filter issues assigned to the authenticated user:
// My issues
await linear.list_issues({ assignee: "me" })
// Team backlog
await linear.list_issues({ team: "ENG", state: "Backlog" })
You can use label names directly in create_issue and update_issue - no need to look up IDs:
await linear.create_issue({
team: "ENG",
title: "Update documentation",
labels: ["documentation", "high-priority"]
})
Label Lookup: Labels can exist at the workspace level or team level. When searching for labels, check both:
list_issue_labels() (no team filter)list_issue_labels({ team: "TEAM" })If a label isn't found at the workspace level, check the team before concluding it doesn't exist.
Use linear api for queries and mutations not supported by MCP tools. See api.md for full documentation.
linear api 'query { viewer { id name } }'
With variables:
linear api 'query($id: String!) { issue(id: $id) { title } }' --variable id=ISSUE_ID
Pipe output through jq for formatting:
linear api 'query { viewer { assignedIssues { nodes { identifier title url } } } }' | jq '.data.viewer.assignedIssues.nodes'
Use the linear:// URL scheme to open issues in the native Mac app instead of the browser:
# Replace https://linear.app with linear:// in any Linear URL
open "linear://team-slug/issue/ENG-123"
The desktop app must be installed. When given an issue identifier (e.g., ENG-123), construct the URL using the team's workspace slug and issue identifier.
api.md