mcp-server-linear

What it does

An MCP server that bridges Claude and Linear's API, exposing tools to create, update, delete, search, and comment on issues; manage projects and milestones; organize issues into parent-child hierarchies; and handle team metadata. It authenticates via personal access tokens or developer tokens and supports working with multiple Linear workspaces simultaneously by prefixing tool names.

Who it's for

Engineers and teams using Linear for issue tracking who want to automate workflows through Claude or Cline. Particularly useful for teams managing multiple Linear workspaces or developers who prefer to create, update, and search issues from within their AI assistant rather than the Linear UI.

Common use cases

• Create, update, and bulk-delete Linear issues from Claude
• Search and filter issues by title, team, or project
• Build hierarchical issue structures with parent and sub-issues
• Manage project milestones and work across multiple Linear workspaces
• Comment on and resolve issues programmatically

Setup pitfalls

• Requires a Linear API token (developer or personal) stored in the LINEAR_ACCESS_TOKEN environment variable — handle as a secret and regenerate if leaked.
• Cline MCP config path varies by OS: macOS uses ~/Library/Application Support/Code/, Windows uses %APPDATA%/Code/, and Linux uses ~/.config/Code/.
• Parent-issue relationships require the parent's UUID, not its identifier like "ENG-123".
• The server reads the filesystem and has no active CI — test locally before relying on complex workflows.