The Linear MCP server is Linear’s official integration. It gives Claude full read/write access to your Linear workspace via OAuth: issues, projects, cycles, comments, and team views. For solo founders and small teams running Linear, this is one of the higher-leverage integrations.
Why use it
Linear is opinionated about issue management. The MCP server matches that ethos: it surfaces structured fields (priority, cycle, assignee) Claude can reason about. “What’s at risk in this cycle?” produces a clear answer instead of a wall of text.
For weekly check-ins, project status reports, and “what should I work on next?” prompts, the Linear server replaces several minutes of manual filtering with one prompt.
What it actually does
Read and create issues, query projects, list cycles, comment on issues, search by label or status, assign work. Pair with the GitHub MCP server for an end-to-end “issue → branch → PR → close issue” flow.
Practical patterns:
- “Show me all P1 issues in the current cycle that haven’t been started.”
- “Create a Linear issue titled ‘fix sitemap lastmod’ with high priority, assign to me.”
- “Summarize what closed in last week’s cycle and what’s slipping.”
Gotchas
OAuth scopes can’t be expanded mid-session. Configure them right at setup. Linear’s default scopes are read-mostly; explicitly grant write if you want issue creation.
Rate limits on the Linear API apply per workspace. Heavy “summarize everything” queries can hit them. Scope queries to specific cycles or teams to stay efficient.
