What Is the Linear MCP Server?
The linear mcp server mcp server setup guide you need starts here. The Linear MCP Server is a Model Context Protocol (MCP) integration that connects AI coding assistants and chat clients directly to your Linear workspace. It exposes Linear’s issue tracking, project management, and team data as structured tools that any MCP-compatible client — Claude Desktop, Cursor, Windsurf — reads and acts on without leaving the conversation. If your team tracks engineering work in Linear, this server lets your AI assistant query issues, create tasks, update statuses, and filter by assignee or cycle in real time.
Linear itself serves over 30,000 engineering teams as of 2026. The MCP server bridges that structured project data into AI workflows, removing the copy-paste loop between your issue tracker and your AI coding environment. For teams already using tools like Cursor or Windsurf for AI-assisted development, this integration closes the gap between “what needs doing” and “doing it.”
Quick Facts
| Field | Value |
|---|---|
| Package | @linear/mcp-server |
| Install | npx @linear/mcp-server |
| Compatible with | Claude Desktop, Cursor, Windsurf, any MCP-compliant client |
| Status | Active (maintained by Linear team, 2026) |
| Auth | Linear API key (Personal Access Token) |
| GitHub | github.com/linear/linear/tree/master/packages/mcp-server |
What You Can Do With It

- Query issues — list open issues by team, assignee, priority, or cycle with natural language prompts
- Create issues — generate new Linear issues with title, description, priority, and team assignment from a single prompt
- Update issue status — move issues through workflow states (Backlog → In Progress → Done) without opening the Linear UI
- Search projects — retrieve project metadata, cycle dates, and completion percentages
- List teams and members — surface team structure for routing and assignment decisions
- Fetch comments — read existing issue comments to give your AI assistant full context before responding
Pairs well with the Jira MCP Server if your org runs hybrid project tracking across both tools. Also complements the Notion MCP Server for teams that document specs in Notion and track execution in Linear.
How to Set It Up
Step 1 — Generate a Linear API key
Go to Linear → Settings → API → Personal API Keys → Create Key. Copy the token.
Step 2 — Install the server
npx @linear/mcp-server
No global install required. npx pulls the latest version on each run.
Step 3 — Configure your MCP client
For Claude Desktop, add this block to claude_desktop_config.json:
{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["@linear/mcp-server"],
"env": {
"LINEAR_API_KEY": "your_api_key_here"
}
}
}
}
For Cursor or Windsurf, add the same block to your MCP settings file (.cursor/mcp.json or .windsurf/mcp.json). See the Cursor Review 2026 for MCP config file locations by OS.
Step 4 — Restart your client and verify
Restart the client. Ask: “List my open Linear issues assigned to me.” A successful response returns structured issue data. If it returns an error, verify the API key has read and write scopes enabled in Linear’s API settings.

Works Best With
| Client | Integration Quality | Notes |
|---|---|---|
| Claude Desktop | ✅ Excellent | Full tool-call support, stable in 2026 |
| Cursor | ✅ Excellent | Native MCP support since Cursor 0.43 |
| Windsurf | ✅ Good | MCP support via Cascade agent |
| GitHub Copilot | ⚠️ Limited | MCP support partial as of mid-2026 |
| VS Code (native) | ⚠️ Limited | Requires MCP extension, experimental |
Teams using GitHub Copilot as their primary coding assistant face limited MCP compatibility — Claude Desktop or Cursor are the reliable choices for this server today.
Known Limitations
- No webhook support — the server is pull-only; it does not push Linear events to your AI client in real time
- Rate limits apply — Linear’s API enforces 1,500 requests per hour on standard plans; heavy automated querying hits this ceiling
- No attachment access — file attachments on issues are not retrievable through the MCP interface
- Workspace scope only — the server connects to one Linear workspace per config block; multi-workspace setups require separate server instances
- No roadmap views — high-level roadmap and initiative data is not exposed as MCP tools in the current version
- npx cold start — first run downloads the package (~2–3 seconds delay); use a cached install for production workflows
For teams managing multiple data sources, the Confluence MCP Server handles documentation-side context while Linear MCP handles execution tracking.
Community Resources

- Linear API Docs — linear.app/docs/api — full GraphQL schema reference
- Linear MCP GitHub — github.com/linear/linear/tree/master/packages/mcp-server — source, issues, changelog
- Linear Community Slack — linear.app/community — active channel for MCP integration questions
- MCP Specification — modelcontextprotocol.io — protocol reference for custom tool extensions
- r/LinearApp — community threads on MCP config edge cases and team workflows
Final Verdict
The Linear MCP Server delivers on its core promise: your AI assistant reads and writes Linear issues without leaving the conversation. Setup takes under 5 minutes if you have a Linear API key ready. The pull-only architecture and single-workspace limit are real constraints for larger orgs, but for individual engineers and small teams, this server removes the context-switching tax between issue tracking and AI-assisted coding.
If you’re building content workflows around your engineering process, → Try Frase integrates with AI tools to turn Linear ticket data into structured content briefs — useful for teams that document features as they ship.
FAQ
Does the Linear MCP Server work with free Linear plans?
Yes. The server uses Linear’s standard API, which is available on all plans including Free. Rate limits are the same across tiers for API access.
Can I create issues with custom fields via MCP?
Custom fields defined in your Linear workspace are partially supported. Standard fields (title, description, priority, assignee, team) work reliably. Custom field writes depend on your workspace schema and the current server version — check the GitHub changelog before relying on this.
Is the Linear API key stored securely?
The key lives in your local MCP config file as a plain environment variable. Do not commit this file to version control. Add claude_desktop_config.json and .cursor/mcp.json to your .gitignore.
How does this compare to the Jira MCP Server?
The Jira MCP Server covers JQL queries and Atlassian-native workflows. Linear MCP is faster to configure and better suited to engineering-first teams on Linear’s modern stack. Choose based on where your team already lives.
Does it support Linear’s cycle (sprint) features?
Yes. You can query active cycles, list issues within a cycle, and retrieve cycle completion percentages. Creating or modifying cycles via MCP is not supported in the current version.



