如何将 Sentry 远程 MCP 连接到 Claude
约 1 分钟即可把 Sentry 的远程 MCP 服务端接入 Claude。如需排查 OAuth / 401 问题,可先用 OAuth 2.1 调试器体检端点。
HTTP + SSEhttps://mcp.sentry.dev/mcp
Legacy SSE endpoint
SSEhttps://mcp.sentry.dev/sse
Install in Cursor →
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp"
}
}
}claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
Install in VS Code →
Or add to .vscode/mcp.json:
{
"servers": {
"sentry": {
"type": "http",
"url": "https://mcp.sentry.dev/mcp"
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.sentry.dev/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": {
"sentry": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.sentry.dev/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"sentry": {
"serverUrl": "https://mcp.sentry.dev/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp"
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.sentry] url = "https://mcp.sentry.dev/mcp"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"sentry": {
"type": "streamableHttp",
"url": "https://mcp.sentry.dev/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"sentry": {
"httpUrl": "https://mcp.sentry.dev/mcp"
}
}
}接入步骤
- 打开连接器设置 — 在 claude.ai → Settings → Connectors 中选择「添加自定义连接器」。
- 填入远程端点 — 将
https://mcp.sentry.dev/mcp粘贴为 Remote MCP Server URL 并保存。 - 完成认证 — 首次调用时客户端会打开 Sentry 的 OAuth 授权页面——点击允许后工具即可用。
- 验证 — 在 在线 Inspector 中粘贴
https://mcp.sentry.dev/mcp并运行 initialize + tools/list 验证连通性。
🧰 工具预览(18)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| find_organizations ~34 tok | 🟢 Read | List Sentry organizations you can access. | — |
| find_teams ~29 tok | 🟢 Read | List teams in an organization. | — |
| find_projects ~31 tok | 🟢 Read | List projects in an organization. | — |
| find_releases ~29 tok | 🟢 Read | List releases of a project. | — |
| search_issues ~33 tok | 🟢 Read | Search Sentry issues using query syntax. | — |
| search_events ~32 tok | 🟢 Read | Search error and transaction events. | — |
| get_issue_details ~31 tok | 🟢 Read | Get details of a Sentry issue. | — |
| update_issue ~32 tok | 🟠 Write | Update an issue's status or assignment. | — |
| analyze_issue_with_seer ~32 tok | 🟢 Read | Ask Seer to analyze an issue. | — |
| create_team ~30 tok | 🟠 Write | Create a team in an organization. | — |
| create_project ~30 tok | 🟠 Write | Create a project in a team. | — |
| update_project ~29 tok | 🟠 Write | Update project settings. | — |
| create_dsn ~30 tok | 🟠 Write | Create a DSN key for a project. | — |
| list_dsns ~28 tok | 🟢 Read | List DSN keys of a project. | — |
| get_doc ~30 tok | 🟢 Read | Fetch a Sentry documentation page. | — |
| search_docs ~29 tok | 🟢 Read | Search Sentry documentation. | — |
| whoami ~30 tok | 🟢 Read | Show the authenticated Sentry user. | — |
| get_issue_event_details ~36 tok | 🟢 Read | Get details of a specific event on an issue. | — |