MCP Directory

How to add Linear MCP Server (official remote) to Claude Desktop

Linear's official hosted MCP server — find, create, and update issues, projects, and comments. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 15, 2026 · 1.6k★ · http · oauth · official

Claude Desktop config for Linear MCP Server (official remote)

Add remote MCP URL https://mcp.linear.app/mcp and complete OAuth
{
  "mcpServers": {
    "linear-mcp-server-official-remote": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.linear.app/mcp"
      ]
    }
  }
}

Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.

Setup steps

  1. 1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
  2. 2Paste the Linear MCP Server (official remote) config below under the top-level "mcpServers" key.
  3. 3Fill in any placeholder secrets (API keys, paths) in the snippet.
  4. 4Save the file, then fully quit and reopen Claude Desktop.
  5. 5Open a chat and confirm Linear MCP Server (official remote)'s tools appear under the 🔌 tools menu.

Before you start

  • A Linear account and workspace (any plan); the server acts with your own user permissions
  • An MCP-capable client that supports remote/HTTP servers (Claude web & desktop, Claude Code, Cursor, VS Code, Codex, Windsurf, Zed, etc.)
  • A browser for the OAuth 2.1 authorization flow — no API key needed for OAuth. Optionally, a Linear API key (from Settings → Security & access) can be passed as an Authorization: Bearer token for headless clients
  • For editors that only support local stdio servers: Node.js 18+ to run the `npx mcp-remote` proxy

What Linear MCP Server (official remote) can do in Claude Desktop

list_issues

List/query issues with filters

get_issue

Fetch a single issue's full details

create_issue

Create a new issue

update_issue

Update an issue (title, description, priority, status, assignee)

list_projects

List projects

get_project

Fetch a project's details

create_project

Create a new project

update_project

Update an existing project

Security

Auth is OAuth 2.1 with dynamic client registration, so no long-lived API key is stored; access respects your existing Linear workspace permissions. Prefer the /mcp Streamable HTTP endpoint over the legacy /sse one.

Linear MCP Server (official remote) + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Linear MCP Server (official remote) config there under the "mcpServers" key and restart the client.

Is Linear MCP Server (official remote) safe to use with Claude Desktop?

Auth is OAuth 2.1 with dynamic client registration, so no long-lived API key is stored; access respects your existing Linear workspace permissions. Prefer the /mcp Streamable HTTP endpoint over the legacy /sse one.

Is this the official Linear MCP server?

Yes. It is hosted by Linear at `https://mcp.linear.app/mcp` and authenticates with your own Linear account, so it respects your existing workspace permissions.

Do I need an API key, or is OAuth enough?

OAuth 2.1 (with dynamic client registration) is the default and needs no API key — you just authorize in the browser. For headless clients you can instead pass a Linear API key as an `Authorization: Bearer` header.

My client only supports local stdio servers — can I still use it?

Yes. Use the `npx -y mcp-remote https://mcp.linear.app/mcp` proxy (requires Node.js 18+), which bridges the remote HTTP server to a local stdio client like older VS Code, Windsurf, or Zed setups.

View repo Full Linear MCP Server (official remote) page