/integration
Removing an integration needs the `org:integrations` permission, which Sentry grants to org owners and managers. If your CLI login predates that scope, `sentry integration delete` asks you to re-authorize before removing anything. This only happens in interactive runs: with
> /plugin marketplace add getsentry/toolkit > /plugin install sentry-mcp@sentry-mcp
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/integration
Context preview
What this command does when you run it.
Removing an integration needs the `org:integrations` permission, which Sentry grants to org owners and managers. If your CLI login predates that scope, `sentry integration delete` asks you to re-authorize before removing anything. This only happens in interactive runs: with
Command definition
integration.mdPermissions
Removing an integration needs the `org:integrations` permission, which Sentry grants to org owners and managers. If your CLI login predates that scope, `sentry integration delete` asks you to re-authorize before removing anything. This only happens in interactive runs: with `--yes` or `--json` the CLI never starts the authorization flow, so run it once without those flags first.
Installing new integrations from the CLI is not supported yet.
This repository contains the Sentry CLI, the Sentry MCP server, and shared packages. For the CLI, see the CLI guide and the published documentation at . The documentation index covers both products and shared contributor guidance.
Other commands on toolkit.
explore
Enter explore mode - think through ideas, investigate problems, clarify requirements
propose
Propose a new change - create it and generate all artifacts in one step

