Sentry MCP Renamed
Sentry's MCP server for issues, events and Seer analysis (repo renamed from sentry-mcp to toolkit).
By defaultCan write
Safest setupNo read-only mode Use a read-only credential
Flagshosted
Labels are provisional (from the project README/docs, checked Oct 27, 2026). Not yet tested in our sandbox.
Read-only switch
Scope is chosen during OAuth. We have not verified a read-only preset.
Preset
No read-only switch. This config is the vendor default plus an approval prompt on every tool. It is not read-only. The credential is what protects you.
Claude Code
.mcp.json
{
"mcpServers": {
"sentry": {
"type": "http",
"url": "https://mcp.sentry.dev/mcp"
}
}
}.claude/settings.json
{
"permissions": {
"ask": ["mcp__sentry"]
}
}ask makes Claude Code prompt before every tool from this server.
Codex
~/.codex/config.toml
# Generated by redpresets.dev on 2026-11-03. Unverified preset. Also use a read-only credential. Not a security guarantee.
[mcp_servers.sentry]
url = "https://mcp.sentry.dev/mcp"
default_tools_approval_mode = "prompt"default_tools_approval_mode = "prompt" asks before every tool call.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp"
}
}
}Don't add write tools to mcpAllowlist in .cursor/permissions.json. Leave them on approval. Cursor's docs say the allowlist is not a security boundary.
Credential layer
Grant read-only org scopes during the OAuth step.
Gotchas
- Repository was renamed from
getsentry/sentry-mcptogetsentry/toolkit.
Facts
- Vendor
- Sentry official
- Source
- getsentry/toolkit
- Hosted endpoint
https://mcp.sentry.dev/mcp- License
- NOASSERTION
- GitHub stars
- 948
- Latest release
- cli@0.47.0 (Oct 5, 2026)
- Last push
- Oct 27, 2026
- Status
- Renamed
- Last checked
- Oct 27, 2026
Sources
- README: hosted URL · checked Oct 27, 2026
Spotted something wrong? Labels change when vendors change. Suggest a correction