Creativity · MCP — server

MCP Linear Server

The MCP Linear Server plugs the Linear issue tracker into the Model Context Protocol. Once authenticated with a Linear API key or OAuth, an MCP client like Claude Desktop or Cursor can search issues, create or update tickets, move them through cycles, and comment on threads — closing the loop between an LLM coding agent and the team's project tracker.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript / Node.js
Transports: stdio, sse

Capabilities

Tools: linear_search_issues, linear_create_issue, linear_update_issue
Tools: linear_list_projects, linear_list_cycles, linear_add_comment
Resources: issue://identifier for full issue context, incl. comments
Auth: personal API key or OAuth (Linear Connect) for shared installs

Install

npx -y @linear/mcp-server

Configuration

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

Frequently asked questions

Where does the Linear API key come from?

In Linear go to Settings → Security & access → Personal API keys → Create new key. Give it read/write scopes for the teams you want the agent to touch and store it in LINEAR_API_KEY.

Can the agent move issues through workflow states?

Yes — linear_update_issue accepts state IDs, assignees, priority, estimate, and cycle. Use linear_list_states to discover valid targets for a given team's workflow.

Should I run the stdio server or the hosted OAuth one?

For personal use, the stdio server with a PAT is simplest. For teams or SaaS deployments use the hosted Linear MCP endpoint with OAuth so each user consents individually and tokens rotate on their own.

Sources

Linear MCP server — accessed 2026-04-20
Linear API overview — accessed 2026-04-20