← MCP

Linear MCPLinear MCP

Linear

MCPMCP 议题管理Issue management 项目管理Project management 远程托管Remote-hosted OAuthOAuth partial lifecycle: active 核验Checked 2026-10-30

Linear 官方 MCP server（mcp.linear.app/mcp）：agent 搜 issue、建 issue、改状态。一条直抓事实：旧 SSE 端点已下线——配置里还写 /sse 的要先换 /mcp。

Linear's official MCP server (mcp.linear.app/mcp): agents search, create and update issues. One direct-fetched fact: the old SSE endpoint is gone — configs still pointing at /sse need to switch to /mcp.

适合与不适合When to use it, when not to

适合：编码 agent 与议题流打通（完成→更新 issue）、需求上下文检索。不适合：要写审批流；非 Linear 栈。

Fits: coding agents closing the loop with issues (finish → update issue), pulling requirement context. Not a fit: write approval flows; non-Linear stacks.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21

出品属地Origin: 国外出品foreign-made　Linear Opus, Inc.（美国）。Linear Opus, Inc. (US).
国内使用Direct access: 大陆可直连direct OK　linear.app 直连实测 200（2026-10-21）。linear.app measured 200 direct (2026-10-21).
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-21 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 它自己不调模型——被 MCP 客户端调用的接口实现。它把 Linear 议题管理（搜 issue、建/改 issue、项目与团队查询）包装成工具给 agent 用。
It calls no model itself — an interface implementation called by MCP clients. It wraps Linear issue management (searching issues, creating/updating issues, querying projects and teams) as tools for agents.
运行位置Where it runs: 官方托管远程 server（mcp.linear.app/mcp——直抓 401=存在需鉴权；旧 /sse 端点 404—— 传输线已换代，直抓核验 2026-10-21）。
Official hosted remote server (mcp.linear.app/mcp — direct fetch 401 = exists but needs auth; the old /sse endpoint 404 — the transport line has changed generations, direct-fetched and verified 2026-10-21).
本地文件Local files: 不碰本机文件系统——作用域是 Linear 云端工作区（issues/projects/teams）。
Never touches the local file system — the scope is the Linear cloud workspace (issues/projects/teams).
关机后的任务Tasks after shutdown: 服务在 Linear 侧；请求-响应语义，无后台任务。
The service lives on Linear's side; request-response semantics, no background tasks.
工具与扩展Tools & extensions: 搜/读/建/改 issue、查项目与团队、评论等；写能力齐全（建 issue、改状态）。完整清单以官方文档为准，未逐条清点。
Search/read/create/update issues, query projects and teams, comments, etc.; write capabilities are complete (create issues, change status). The complete inventory follows the official docs; it has not been enumerated item by item.
上下文与记忆Context & memory: 无 server 侧跨会话记忆——状态在 Linear 工作区本身。
No server-side cross-session memory — state lives in the Linear workspace itself.
权限与限制Permissions & limits: OAuth 用户鉴权：agent 可见面=所连 Linear 账号权限；写操作直接生效，无工具级审批机制的官方说明——接 agent 前按「它能替你建改 issue」设防。
OAuth user auth: the agent-visible surface = the connected Linear account's permissions; write operations take effect directly, and there is no official docs for a tool-level approval mechanism — before hooking up an agent, defend on the assumption "it can create and edit issues for you".
适合什么任务Best for: 适合：编码 agent 干完活顺手建/更新 issue、从 Linear 拉「这个需求当时怎么说的」。不适合：要审批流的严格写管控；非 Linear 栈。
Fits: coding agents creating/updating issues as they finish work, pulling "what did this requirement say back then" from Linear. Not a fit: strict write control needing approval flows; non-Linear stacks.
传输方式Transport: Streamable HTTP（mcp.linear.app/mcp）；旧 SSE 端点已下线（直抓 404 核验）。核验：linear.app/docs/mcp 200、端点 401（2026-10-21）。
Streamable HTTP (mcp.linear.app/mcp); the old SSE endpoint is retired (direct fetch 404 verified). Verified: linear.app/docs/mcp 200, endpoint 401 (2026-10-21).
认证机制Authentication: OAuth 浏览器授权流（首次连接登录 Linear 账号）；无 PAT 明文配置路线的官方说明。授权粒度与令牌吊销细节未逐条核验。
OAuth browser authorization flow (log into the Linear account on first connection); no official docs for a plaintext-PAT configuration route. Authorization granularity and token-revocation details not verified item by item.
权限范围Permission scope: 读面：issue 搜索/读取、项目与团队查询；写面：建/改 issue、评论。跟着账号权限走；无独立审批层。
Read surface: issue search/read, project and team queries; write surface: create/update issues, comments. It follows the account's permissions; there is no separate approval layer.

头号误解Top misconception

用旧 /sse 端点配置——已 404（2026-10-21 直抓），现役 /mcp（Streamable HTTP）Configuring the old /sse endpoint — it 404s (direct-fetched 2026-10-21); the live endpoint is /mcp (Streamable HTTP)
把「连上」当「能看全部」——可见面跟着所连账号权限Assuming 'connected' means 'sees everything' — visibility follows the connected account's permissions
写操作无审批——agent 建 issue/改状态直接生效Writes have no approval — agent-created issues and status changes take effect immediately

未知项清单Known unknowns

工具全清单（未逐条清点）
速率限制细则（官方未给数字）
工作区级管控面（未逐条核验）

The full tool inventory (not enumerated item by item)
Rate-limit details (official gives no numbers)
The workspace-level control surface (not verified item by item)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-21。

类型Type	名称Name	链接Link
docs	Linear · 官方 MCP 文档（端点与鉴权口径，2026-10-21 直抓核验）Linear · official MCP docs (endpoint and auth wording, direct-fetched and verified 2026-10-21)	https://linear.app/docs/mcp
changelog	Linear · 官方 changelog（changelog）Linear · official changelog (changelog)	https://linear.app/changelog
docs	Linear · MCP 入口页（直抓 200）Linear · MCP entry page (direct fetch 200)	https://linear.app/mcp

实测记录Measured runs

本档未在真实客户端逐项跑通；工具清单与权限来自官方 README。

This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.