
Linear MCP Server (official remote)
OfficialLinear's official hosted MCP server — find, create, and update issues, projects, and comments.
Add to your client
Copy the config for your MCP client and paste it into its config file.
Add remote MCP URL https://mcp.linear.app/mcp and complete OAuthPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"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.
Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
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
About Linear MCP Server (official remote)
Linear's official, fully-hosted remote MCP server. It exposes your Linear workspace — issues, projects, comments, cycles, documents, teams, and users — to any MCP-capable client (Claude, Cursor, VS Code, Codex, Windsurf, Zed, and more) over a single HTTP endpoint at https://mcp.linear.app/mcp.
Because it is remote and OAuth-backed, there is nothing to install, run, or keep updated locally — you connect the URL, authorize in your browser, and the server acts with your own Linear permissions. The tool surface is a deliberately curated abstraction over Linear's GraphQL API rather than a 1:1 mapping, so common agent tasks (create an issue, move it through a workflow, leave a comment, look up a project) map to clean, simple tools.
Use it to let an AI assistant triage and file issues, draft project updates, summarize what a team is working on, or pull issue context directly into your editor without leaving the conversation.
Tools & capabilities (15)
list_issuesList/query issues with filters
get_issueFetch a single issue's full details
create_issueCreate a new issue
update_issueUpdate an issue (title, description, priority, status, assignee)
list_projectsList projects
get_projectFetch a project's details
create_projectCreate a new project
update_projectUpdate an existing project
list_commentsList comments on an issue
create_commentAdd a comment to an issue
list_teamsList teams in the workspace
list_usersList workspace users
list_issue_statusesList workflow statuses
list_issue_labelsList issue labels
search_documentationSearch Linear's product documentation
What this server can do
Linear MCP Server (official remote) provides tools for these capabilities — tap one to see every MCP server that does the same:
When to use it
- Use it when you want an AI assistant to file or triage Linear issues from a chat or your editor
- Use it when you need to move issues through your workflow (assign, prioritize, change status) by natural language
- Use it when you want to summarize what a team or project is working on without opening Linear
- Use it when pulling issue/project context into Cursor, VS Code, or Claude Code while coding
- Use it when generating issues from meeting notes, bug reports, or support threads
- Use it when you want a zero-install, always-current integration governed by your own Linear permissions
Quick setup
- 1Pick your client and add the remote server URL `https://mcp.linear.app/mcp` (e.g. Claude Code: `claude mcp add --transport http linear-server https://mcp.linear.app/mcp`)
- 2For editors without native remote support, configure `npx -y mcp-remote https://mcp.linear.app/mcp` as the command
- 3Start the client and complete the browser-based OAuth 2.1 sign-in to authorize your Linear workspace
- 4Restart/reload the client so it discovers the Linear tools
- 5Verify by asking the assistant to list your recent issues or create a test issue
Security notes
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) FAQ
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.
What can it actually do — does it cover the whole Linear API?
It exposes a curated set of ~20 tools for issues, projects, comments, cycles, documents, teams, users, labels, and statuses — not a full GraphQL mirror. Linear notes more functionality is being added over time.
Does it cost anything?
The MCP server itself is provided by Linear at no additional charge; you only need a Linear account. Actions are limited to what your plan and permissions already allow.
Alternatives to Linear MCP Server (official remote)
Compare all alternatives →AI-powered task-management system for AI-driven development that drops into Cursor, Windsurf, Claude Code, and more.
Gives AI assistants deep knowledge of 2,000+ n8n nodes, plus optional workflow management on your own n8n instance.
Background computer-use MCP server that drives native macOS, Windows, and Linux desktop apps without stealing focus.
Compare Linear MCP Server (official remote) with: