What it does & operational scope
Linear MCP Server equips coding agents with direct issue management capabilities through Linear's GraphQL API. Running locally over stdio, it exposes operations to query backlogs, read detailed issue descriptions, update ticket statuses, assign engineering cycles, and author structured defect reports with markdown reproduction steps.
Linear MCP Server is an open-source Model Context Protocol server licensed under MIT that exposes Linear issue backlogs, bug tracking, and cycle management over stdio.
Your AI coding agent requires live access to Linear tools and resources over local IPC or streamable transport.
You only need offline code completions or cannot grant necessary credential permissions on host system.
Client configuration & wire setup
Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.
claude_desktop_config.json{ "mcpServers": { "linear": { "command": "npx", "args": ["-y", "linear-mcp-server"], "env": { "LINEAR_API_KEY": "<YOUR_API_KEY>" } } }}Exposed tool endpoints & primitives
Discovered MCP Tools
4 Tools Readylist_issues🟢 Read-Only (Safe)Query team issues with status, project, assignee, and priority filters
create_issue🟡 State MutationDraft and file a new Linear issue with title, markdown body, and team ID
update_issue🟡 State MutationModify issue state, estimate, assignee, or priority level
get_project🟢 Read-Only (Safe)Inspect project roadmap status, progress metrics, and member lists
Scopes, secret storage, and sandbox boundaries
Run Linear MCP Server with scoped environment tokens. Never run under root and restrict network ingress.Real conversational prompts & expected tool calls
💬 "Find latest technical updates for Linear MCP Server from the last 7 days"list_issues({ query: "Linear MCP Server updates", limit: 5 })Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.
💬 "Inspect status and health boundaries for Linear MCP Server"list_issues_status({ verbose: true })Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.
Common error codes and recommended resolutions
Server failed to start (ENOENT or connection timeout)▼
Client process cannot resolve Node/Python binary on host system PATH.
Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").
Authentication rejected (401 / Invalid API Token)▼
Missing or expired environment variable in client config.
Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.
Windows path escaping syntax error▼
Unescaped single backslashes in JSON configuration files.
Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").
Technical trade-offs and operational friction
+ Bridges issue backlog specifications directly into AI coding loops.
+ Fast GraphQL execution with clean markdown representation of issue tasks.
+ Maintains sprint status hygiene without manual engineer board updates.
− Rapid issue queries and bulk comment updates trigger Linear GraphQL rate limits (1,500 requests per hour), pausing execution loops.
− Lacks support for custom enterprise fields and webhook subscriptions, restricting agents to standard issue and project attributes.
Side-by-side rival comparisons
Compare Linear MCP Server vs Atlassian Jira & Confluence MCP Server across transport protocols and exposed tools.
Enter ShowdownJSON-RPC 2.0 wire trace & receipts
Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
1{2 "jsonrpc": "2.0",3 "id": 1,4 "method": "tools/call",5 "params": {6 "name": "inspect",7 "arguments": {}8 }9}
