← MCP

Sentry MCP / ToolkitSentry MCP / Toolkit

Sentry

MCPMCP 监控诊断Monitoring and diagnostics SentrySentry 远程托管Remote-hosted FSLFSL partial lifecycle: active 核验Checked 2026-10-30

Sentry 官方的 agent 工具线：把「查崩溃、看事件、对 release」包成 MCP 工具，编码 agent 能直接问「这个报错线上有没有」。诚实标注：旧仓 sentry-mcp 已 redirect 到 getsentry/toolkit；许可是 FSL-1.1-Apache-2.0——不是纯 Apache，生产用途有限制期。

Sentry's official agent tooling line: crashes, events and releases wrapped as MCP tools, so a coding agent can ask 'is this error live?'. Honest notes: the old sentry-mcp repo now redirects to getsentry/toolkit; the license is FSL-1.1-Apache-2.0 — not plain Apache, production use has a restriction window.

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

适合：编码/运维 agent 接 Sentry 诊断流、线上事故时让 agent 拉 issue 上下文。不适合：本地日志分析（不在作用域）；FSL 限制期内的闭源商用集成。

Fits: coding/ops agents plugging Sentry into diagnosis flows; pulling issue context during incidents. Not a fit: local log analysis (out of scope); closed-source commercial integration inside the FSL restriction window.

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

出品属地Origin: 国外出品foreign-made　Sentry（Functional Software, Inc.，美国）。Sentry (Functional Software, Inc., US).
国内使用Direct access: 直连不可达direct blocked　github.com 直连实测 000（波动，同日代理可达 200）；mcp.sentry.dev 直连未测——大陆可达性未逐条核验。github.com measured 000 direct (fluctuating; 200 via proxy the same day); mcp.sentry.dev mainland reachability not individually verified.
备案状态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 客户端调用的接口实现，选模型是客户端的事。它把 Sentry 平台能力（issue、事件、release、告警）包装成 MCP 工具供 agent 查询与诊断。
It calls no model itself — an interface implementation called by MCP clients; choosing the model is the client's business. It wraps Sentry platform capabilities (issues, events, releases, alerts) as MCP tools for agents to query and diagnose.
运行位置Where it runs: 官方托管远程 server 为主（mcp.sentry.dev 直抓 200）；仓 getsentry/toolkit 是官方工具线（949★，最近推送 2026-10-30，GitHub API 核验）。旧仓名 getsentry/sentry-mcp 已 redirect（直抓所见）。
Mainly the official hosted remote server (mcp.sentry.dev direct fetch 200); the getsentry/toolkit repo is the official tooling line (949★, last push 2026-10-30, GitHub API verified). The old repo name getsentry/sentry-mcp now redirects (seen in the direct fetch).
本地文件Local files: 不碰本机文件系统——它操作的是 Sentry 云端数据（issue/事件/release）。本地日志与源码不在它作用域内；要读本地文件得配 filesystem server。
Never touches the local file system — it operates on Sentry cloud data (issues/events/releases). Local logs and source code are outside its scope; reading local files requires pairing a filesystem server.
关机后的任务Tasks after shutdown: 远程托管形态与客户端进程无关，服务在 Sentry 侧；无断点续跑语义—— MCP 会话模式是请求-响应，官方未提供后台任务机制。
The hosted form is independent of the client process; the service lives on Sentry's side; no resume-from-checkpoint semantics — the MCP session model is request-response, the official side provides no background-task mechanism.
工具与扩展Tools & extensions: 面向「agent 查崩溃/诊断线上问题」的工具集：whoami、找 issue、看 issue 详情、事件与堆栈、release 对比等；完整工具清单以官方文档为准，未逐条清点。
A toolset aimed at "agents checking crashes/diagnosing production issues": whoami, find issues, view issue details, events and stacks, release comparisons, etc.; the complete tool inventory follows the official docs, not enumerated item by item.
上下文与记忆Context & memory: 无跨会话记忆——每次会话独立，状态在 Sentry 平台本身。官方未提供 server 侧记忆或检索层（未核验到≠没有，已查文档未见）。
No cross-session memory — each session is independent, state lives in the Sentry platform itself. The official side provides no server-side memory or retrieval layer (not verified ≠ absent; docs checked showed none).
权限与限制Permissions & limits: 权限由 Sentry 账号鉴权决定（OAuth 登录流）；能读 issue 与事件数据，写操作面（如解决 issue）以官方工具清单为准——未逐条核验写能力边界。
Permissions are determined by Sentry account auth (OAuth login flow); it can read issue and event data, the write surface (e.g. resolving issues) follows the official tool inventory — write-capability boundaries not verified item by item.
适合什么任务Best for: 适合：编码 agent 直接查「这个报错在 Sentry 里有没有」、线上事故诊断接 agent 工作流。不适合：要本地日志分析（不在作用域）；要 FSL 限制期内的闭源商用集成（先读许可条款）。
Fits: coding agents directly asking "does this error exist in Sentry", hooking production-incident diagnosis into agent workflows. Not a fit: local log analysis (out of scope); closed-source commercial integrations during the FSL restriction window (read the license terms first).
传输方式Transport: 官方主推 Streamable HTTP 远程托管（mcp.sentry.dev）；客户端配置以官方文档为准。SSE 老传输的支持状态未逐条核验。核验：官方文档页与 mcp.sentry.dev 直抓 200（2026-10-21）。
Officially primary Streamable HTTP remote hosting (mcp.sentry.dev); client configuration follows the official docs. Support status of the older SSE transport not verified item by item. Verified: official docs page and mcp.sentry.dev direct fetch 200 (2026-10-21).
认证机制Authentication: 走 Sentry 账号 OAuth 登录流（浏览器授权）；无 PAT 明文配置路线的官方说明—— 未逐条核验。凭据存储与轮换细节官方未展开。
Goes through the Sentry account OAuth login flow (browser authorization); no official docs for a plaintext-PAT configuration route — not verified item by item. Credential storage and rotation details are not expanded in the official docs.
权限范围Permission scope: 作用域 = Sentry 账号可见的 org/project 数据面；读 issue/事件为主。写操作与高危工具清单未逐条核验；无独立审批机制的官方说明。
Scope = the org/project data visible to the Sentry account; reading issues/events is primary. The write operations and high-risk tool inventory not verified item by item; no official docs for a separate approval mechanism.

头号误解Top misconception

用旧仓名 sentry-mcp 找仓库——现 redirect 到 getsentry/toolkit（2026-10-21 直抓核验）Using the old sentry-mcp repo name — it now redirects to getsentry/toolkit (direct-fetched 2026-10-21)
把 FSL 当 Apache——FSL-1.1 有生产用途限制期，到期才转 Apache 2.0Reading FSL as Apache — FSL-1.1 has a production-use restriction window before it converts to Apache 2.0
把「查 issue」当「能修 issue」——写能力边界未逐条核验，别按读能力推写能力Assuming 'query issues' means 'fix issues' — write-capability boundaries are not individually verified; do not infer write from read

未知项清单Known unknowns

完整工具清单与写操作边界（未逐条清点）
SSE 传输支持状态（未逐条核验）
FSL 各版本 change date（未逐条核验——用前查 LICENSE.md 当前条款）

The complete tool inventory and write-operation boundaries (not enumerated item by item)
SSE transport support status (not verified item by item)
The change date of each FSL version (not verified item by item — check the current LICENSE.md terms before use)

证据来源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
repo	getsentry/toolkit · 仓库（FSL-1.1-Apache-2.0；949★，最近推送 2026-10-30，GitHub API 核验）getsentry/toolkit · repository (FSL-1.1-Apache-2.0; 949★, last push 2026-10-30, GitHub API verified)	https://github.com/getsentry/toolkit
docs	getsentry/toolkit · LICENSE.md（FSL-1.1-Apache-2.0 原文，2026-10-21 直抓核验）getsentry/toolkit · LICENSE.md (FSL-1.1-Apache-2.0 original text, direct-fetched and verified 2026-10-21)	https://github.com/getsentry/toolkit/blob/main/LICENSE.md
docs	Sentry MCP · 官方托管端点页（直抓 200）Sentry MCP · official hosted endpoint page (direct fetch 200)	https://mcp.sentry.dev
changelog	getsentry/toolkit · Releases（changelog）getsentry/toolkit · Releases (changelog)	https://github.com/getsentry/toolkit/releases

实测记录Measured runs

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

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