Linear Official Remote MCP Server
Linear's hosted MCP endpoint (mcp.linear.app) exposes issue tracking to any MCP client. OAuth 2.1 with DCR means clients like Cursor and Claude register themselves automatically โ connect once and your issues are one prompt away.
- Provider
- Linear Orbit Inc. โ
- Categories
- ๐ Project Management & Productivity๐ ๏ธ Developer Tools & Git
ไธญๆ็ฎไป
Linear ๅฎๆน่ฟ็จ MCP ๆๅกๅจ๏ผๆฏๆ Streamable HTTP ไธ SSE ไธค็งไผ ่พใAI ไปฃ็ๅฏๆ็ดขใๅๅปบใๆดๆฐๅทฅๅๅนถๆฅ่ฏขๅข้ๅทฅไฝๆตใ
Legacy SSE endpoint
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"linear": {
"url": "https://mcp.linear.app/mcp"
}
}
}claude mcp add --transport http linear https://mcp.linear.app/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"linear": {
"type": "http",
"url": "https://mcp.linear.app/mcp"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.linear.app/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"linear": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.linear.app/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"linear": {
"serverUrl": "https://mcp.linear.app/mcp"
}
}
}๐งฐ Tools exposed by Linear MCP (4)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| linear_search_issues | ๐ข Read | Search Linear issues by text, team, state or assignee. | query*: stringteam: stringstate: string |
| linear_create_issue | ๐ Write | Create a new issue in a Linear team. | title*: stringteam*: stringdescription: stringpriority: number |
| linear_update_issue | ๐ Write | Update fields on an existing Linear issue. | issueId*: stringstate: stringassignee: string |
| linear_get_user_issues | ๐ข Read | List issues assigned to a Linear user. | user: stringstate: string |
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Scopes
readwrite- Protected resource metadata
- https://mcp.linear.app/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Guide
Linear MCP โ Remote MCP Server
Linear was one of the first major SaaS vendors to ship a first-party remote MCP server, and it is still the reference implementation most other vendors copy. It speaks both the modern Streamable HTTP transport at /mcp and the legacy HTTP+SSE transport at /sse, and it implements the full OAuth 2.1 discovery flow including Dynamic Client Registration, so compliant clients connect with zero manual configuration.
Endpoint & Transport
- Endpoint URL:
https://mcp.linear.app/mcp - Legacy SSE endpoint:
https://mcp.linear.app/sse - Transport: Streamable HTTP + legacy SSE
Authentication
Linear MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Available Tools (4)
| Tool | Safety | Description |
|---|---|---|
linear_search_issues |
read | Search Linear issues by text, team, state or assignee. |
linear_create_issue |
write | Create a new issue in a Linear team. |
linear_update_issue |
write | Update fields on an existing Linear issue. |
linear_get_user_issues |
read | List issues assigned to a Linear user. |
Connect in 30 Seconds
Claude Code โ one command:
claude mcp add --transport http linear https://mcp.linear.app/mcp
Cursor โ add to ~/.cursor/mcp.json:
{ "mcpServers": { "linear": { "url": "https://mcp.linear.app/mcp" } } }
VS Code โ add to .vscode/mcp.json:
{ "servers": { "linear": { "type": "http", "url": "https://mcp.linear.app/mcp" } } }
Claude Desktop & stdio clients โ bridge with mcp-remote:
{ "mcpServers": { "linear": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"] } } }
On first connect your client opens a browser OAuth consent screen โ approve it and tools become available immediately.
Troubleshooting
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - Which URL should I use? Prefer
https://mcp.linear.app/mcp(Streamable HTTP). The SSE URL is only for older clients pinned to the pre-2025-03-26 spec. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - New clients should prefer /mcp; the /sse endpoint exists for older clients that only implement the legacy SSE transport.
- OAuth access is scoped to the workspaces you approve during the consent flow.
๐ How to Connect
- Copy the Linear MCP endpoint URLThe remote endpoint is https://mcp.linear.app/mcp. A legacy SSE endpoint is also available at https://mcp.linear.app/sse.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http linear https://mcp.linear.app/mcp. Cursor: add"linear": { "url": "https://mcp.linear.app/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Linear Orbit Inc. consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.linear.app/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Linear MCP's 4 tools respond.
โ FAQ
What is the Linear MCP remote MCP endpoint?
The primary endpoint is https://mcp.linear.app/mcp, with a legacy SSE endpoint at https://mcp.linear.app/sse. It is an official first-party server operated by Linear Orbit Inc., speaking the Streamable HTTP + legacy SSE transport.
Should I use Linear MCP's /mcp or /sse endpoint?
Use https://mcp.linear.app/mcp โ Streamable HTTP is the current MCP transport and what every modern client defaults to. https://mcp.linear.app/sse exists only for clients still on the legacy HTTP+SSE transport from the 2024 spec.
How do I authenticate with Linear MCP?
Linear MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Linear MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Linear MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http linear https://mcp.linear.app/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge.
What tools does Linear MCP expose?
4 tools are cataloged in this directory โ including `linear_search_issues`, `linear_create_issue`, `linear_update_issue` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
Notion's official hosted MCP server. Agents can search your workspace, read and create pages, and query databases over Streamable HTTP or SSE.
Atlassian's official remote MCP server for Jira and Confluence. Search and create issues and pages over the legacy SSE transport with OAuth 2.1.
Asana's official remote MCP server. Agents can search tasks, create work items and read project structure over the SSE transport with OAuth.
Intercom's official remote MCP server for customer support data. Agents can search conversations, look up contacts and reply to threads over OAuth.