/react-native
```bash
> /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
/react-native
Context preview
What this command does when you run it.
```bash
Command definition
react-native.mdExamples
# Upload a bundle + sourcemap by debug ID (called by the Gradle plugin)
sentry react-native gradle \
--bundle index.android.bundle \
--sourcemap index.android.bundle.map
# Also associate with a release and distribution(s)
sentry react-native gradle \
--bundle index.android.bundle \
--sourcemap index.android.bundle.map \
--release com.example.app@1.0.0 \
--dist 1000
# Xcode build phase (usually added automatically to your build script)
sentry react-native xcode
Xcode build step (`react-native xcode`)
`react-native xcode` runs inside an Xcode "Bundle React Native code and images" build phase. It has three modes:
- **release build** — wraps the RN build script (standing in for
`NODE_BINARY`/`HERMES_CLI_PATH`) to capture the produced bundle + sourcemap (including the Hermes combined sourcemap), then uploads them.
- **simulator build with `--allow-fetch`** — downloads the bundle + sourcemap
from the running packager, then uploads.
- **debug build** — just runs the build script.
Release/distribution come from `SENTRY_RELEASE`/`SENTRY_DIST` or the app's `Info.plist` (`<CFBundleIdentifier>@<CFBundleShortVersionString>+<CFBundleVersion>`), unless `--no-auto-release` is set. When run outside an Xcode build phase the release is discovered via `xcodebuild`; `--allow-xcode-infoplist-preprocessing` enables `cc`-based `INFOPLIST_PREPROCESS` handling. Pass extra build-script arguments after the flags.
Important Notes
- `react-native gradle` is normally invoked automatically by the
[sentry-android-gradle-plugin](https://docs.sentry.io/platforms/react-native/sourcemaps/); you rarely run it by hand.
- It injects a debug ID into both the bundle and its sourcemap, then uploads
them under the `~/<filename>` convention. Without `--release` the files are matched by debug ID; with `--release` they are also uploaded for each `--dist`.
- `--wait`/`--wait-for` block until the server finishes processing the upload.
- Indexed/file RAM bundles (a pre-Hermes format that React Native has since
deprecated) are not supported — use a plain or Hermes bundle.
Read more
Examples
# Upload a bundle + sourcemap by debug ID (called by the Gradle plugin) sentry react-native gradle \ --bundle index.android.bundle \ --sourcemap index.android.bundle.map # Also associate with a release and distribution(s) sentry react-native gradle \ --bundle index.android.bundle \ --sourcemap index.android.bundle.map \ --release com.example.app@1.0.0 \ --dist 1000 # Xcode build phase (usually added automatically to your build script) sentry react-native xcode
Xcode build step (`react-native xcode`)
`react-native xcode` runs inside an Xcode "Bundle React Native code and images" build phase. It has three modes:
- **release build** — wraps the RN build script (standing in for
`NODE_BINARY`/`HERMES_CLI_PATH`) to capture the produced bundle + sourcemap (including the Hermes combined sourcemap), then uploads them.
- **simulator build with `--allow-fetch`** — downloads the bundle + sourcemap
from the running packager, then uploads.
- **debug build** — just runs the build script.
Release/distribution come from `SENTRY_RELEASE`/`SENTRY_DIST` or the app's `Info.plist` (`<CFBundleIdentifier>@<CFBundleShortVersionString>+<CFBundleVersion>`), unless `--no-auto-release` is set. When run outside an Xcode build phase the release is discovered via `xcodebuild`; `--allow-xcode-infoplist-preprocessing` enables `cc`-based `INFOPLIST_PREPROCESS` handling. Pass extra build-script arguments after the flags.
Important Notes
- `react-native gradle` is normally invoked automatically by the
[sentry-android-gradle-plugin](https://docs.sentry.io/platforms/react-native/sourcemaps/); you rarely run it by hand.
- It injects a debug ID into both the bundle and its sourcemap, then uploads
them under the `~/<filename>` convention. Without `--release` the files are matched by debug ID; with `--release` they are also uploaded for each `--dist`.
- `--wait`/`--wait-for` block until the server finishes processing the upload.
- Indexed/file RAM bundles (a pre-Hermes format that React Native has since
deprecated) are not supported — use a plain or Hermes bundle.
Sentry's MCP service is primarily designed for human-in-the-loop coding agents. Our tool selection and priorities are focused on developer workflows and debugging use cases, rather than providing a general-purpose MCP server for all Sentry functionality.
Repo: getsentry/sentry-mcp
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

