Linear MCP Server: Setup Guide, Use Cases & Limitations

What Is Linear MCP Server?

Linear MCP Server is an MCP integration maintained by Linear that lets you manage issues, projects, and teams in Linear directly from Claude Code or Claude Desktop. It exposes Linear’s project management functionality through the Model Context Protocol so Claude can read and write to your Linear workspace during a session.

Quick Facts

What You Can Do With It

• Issue creation: Ask Claude to create Linear issues with titles, descriptions, assignees, and labels without leaving your editor.
• Project tracking: Query the current state of projects and surface progress updates directly in your conversation context.
• Sprint planning: Review and organize work into cycles by interacting with Linear’s sprint data through Claude.
• Bug reporting: File structured bug reports into Linear from Claude Code, pulling in relevant context from your current session.

How to Set It Up

You will need a Linear API key before starting. Generate one at Linear → Settings → API → Personal API Keys.

Run directly with npx:

npx @linear/linear-mcp
**Claude Code config (`.claude/mcp.json`):**

```json
{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": ["@linear/linear-mcp"],
      "env": {
        "LINEAR_API_KEY": "your_linear_api_key_here"
      }
    }
  }
}

Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": ["@linear/linear-mcp"],
      "env": {
        "LINEAR_API_KEY": "your_linear_api_key_here"
      }
    }
  }
}

Replace your_linear_api_key_here with your actual key. The server reads this environment variable at startup; without it, requests to Linear’s API will fail with an authentication error.

Works Best With

This server is documented as compatible with Claude Code and Claude Desktop. Claude Code is the primary target use case — the integration fits naturally into development workflows where you want to log issues or check project state without switching to a browser. Claude Desktop works equally well for non-coding contexts such as reviewing sprint status or drafting bug reports.

Known Limitations

• Authentication is required: The server will not start usefully without a valid LINEAR_API_KEY. Scopes granted to that key determine what the server can access — a read-only key cannot create or mutate issues.
• Rate limits: Linear’s API enforces rate limits on its GraphQL endpoint. Heavy automated use (bulk issue creation, repeated queries) may hit these limits. Check Linear’s API documentation for current rate limit details.
• Workspace scope: The API key is tied to a single Linear workspace. Switching workspaces requires a different key.
• No offline support: All operations require a live connection to Linear’s API; there is no local cache or offline fallback.
• npx cold starts: Running via npx means the package is fetched on first use. Pin a specific version in your config if you need reproducible behavior across machines.

Community Resources

• GitHub Issues: https://github.com/linear/linear-mcp/issues — the primary place to report bugs or check known issues
• Linear Developer Docs: https://developers.linear.app/docs — covers API scopes, rate limits, and GraphQL schema
• MCP Community (Reddit): Search r/ClaudeAI for threads on Linear MCP usage and configuration tips