com.mcparmory/sentry
OCI · GHCR.IO/MCPARMORY/SENTRY:1.0.2 · 2 COMPONENTS · SCANNED SEP 20
Track errors, manage performance alerts, and configure dashboards and monitors
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 33368 tokens (~166/item across 200 items; 200 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety99
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 31 of 32 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "create_deploy_for_release" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 200 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/sentry MCP server?
com.mcparmory/sentry runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/sentry:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/sentry:1.0.2
claude mcp add com-mcparmory-sentry -- docker run --rm -i ghcr.io/mcparmory/sentry:1.0.2
{
"mcpServers": {
"com-mcparmory-sentry": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
]
}
}
} {
"servers": {
"com-mcparmory-sentry": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
]
}
}
} codex mcp add com-mcparmory-sentry -- docker run --rm -i ghcr.io/mcparmory/sentry:1.0.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-sentry": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-sentry:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/sentry:1.0.2"] {
"McpServers": {
"com-mcparmory-sentry": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
]
}
}
} {
"mcpServers": {
"com-mcparmory-sentry": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/sentry:1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_tag_values List Tag Values ~110
Retrieve all values associated with a specific tag key in a project. Supports filtering values using a contains-based query parameter and returns up to 1000 results per page.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The tag key name to retrieve associated values for. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
list_tag_values_for_issue List Tag Values for Issue ~134
Retrieve all values associated with a specific tag key for an issue, useful for understanding what tags have been applied and their values. Returns up to 1000 values when paginated.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Optional list of environment names to filter tag values by. When specified, only values from the listed environments are returned. |
| issue_id | integer | yes | The numeric identifier of the issue to query for tag values. |
| key | string | yes | The tag key name to retrieve associated values for. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
No output schema declared.
No examples provided.
list_team_members List Team Members ~91
Retrieve all active members of a team within an organization. Note that members with pending invitations are excluded from the results.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL slug of the organization. |
| team_id_or_slug | string | yes | The team identifier, which can be either the numeric ID or the URL slug of the team within the organization. |
No output schema declared.
No examples provided.
list_team_projects List Team Projects ~92
Retrieve all projects associated with a specific team within an organization. Returns a list of projects bound to the team.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| team_id_or_slug | string | yes | The team identifier, which can be either the numeric ID or the URL-friendly slug of the team within the organization. |
No output schema declared.
No examples provided.
list_teams_for_project List Teams for Project ~83
Retrieve all teams that have access to a specific project within an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL-friendly slug of the project. |
No output schema declared.
No examples provided.
list_test_results_for_repository List Test Results for Repository ~184
Retrieves a paginated list of test results for a specific repository, with optional filtering by test status, branch, and name substring matching.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Limit results to a specific branch. If omitted, results from all branches are included. |
| filterBy | string | – | Filter results by test category: flaky tests, failed tests, slowest tests, or skipped tests. If omitted, all test results are returned. |
| limit | integer | – | Maximum number of results to return per page. Defaults to 20 if not specified. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| owner | string | yes | The repository owner or account name. |
| repository | string | yes | The repository name. |
| term | string | – | Filter test results by name substring using case-sensitive contains matching. |
No output schema declared.
No examples provided.
list_test_suites_for_repository List Test Suites for Repository ~107
Retrieves all test suites associated with a repository's test results, with optional filtering by name substring.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| owner | string | yes | The owner or account name that owns the repository. |
| repository | string | yes | The name of the repository to retrieve test suites from. |
| term | string | – | Optional substring to filter test suites by name using case-sensitive contains matching. |
No output schema declared.
No examples provided.
list_user_teams_in_organization List User Teams in Organization ~72
Retrieve all teams within an organization that the authenticated user has access to. This endpoint requires user authentication tokens and is useful for discovering team membership and permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
No output schema declared.
No examples provided.
list_users_who_viewed_replay List Users Who Viewed Replay ~129
Retrieve a list of users who have viewed a specific replay within a project. Useful for understanding replay engagement and visibility.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. Used to scope the resource within your organization. |
| project_id_or_slug | string | yes | The project identifier, either as a numeric ID or URL-friendly slug. Used to scope the replay within a specific project. |
| replay_id | string | yes | The unique identifier of the replay in UUID format. Specifies which replay's viewers you want to retrieve. |
No output schema declared.
No examples provided.
regenerate_repository_upload_token Regenerate Repository Upload Token ~95
Regenerates an existing repository upload token, invalidating the previous token and returning a new one for repository uploads.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| owner | string | yes | The owner identifier of the repository, typically a user or organization name. |
| repository | string | yes | The name of the repository for which to regenerate the upload token. |
No output schema declared.
No examples provided.
remove_member_from_team Remove Member from Team ~108
Remove an organization member from a specific team. Requires appropriate authorization scopes; org:read scope can only remove yourself from teams you belong to.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The numeric ID of the organization member to remove from the team. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL slug of the team. |
No output schema declared.
No examples provided.
remove_service_hook Remove Service Hook ~95
Delete a service hook from a project. This removes the webhook integration and stops it from receiving events.
| Name | Type | Req | Description |
|---|---|---|---|
| hook_id | string | yes | The unique identifier (GUID) of the service hook to remove. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
resolve_event_id Resolve Event ID ~90
Resolves an event ID to retrieve the associated project slug, internal issue ID, and internal event ID for a given organization.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The event ID to resolve. This is the unique identifier for the event you want to look up. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
No output schema declared.
No examples provided.
resolve_short_id Resolve Short ID ~104
Resolve a short issue ID to retrieve the associated project slug and group (issue) details. This allows you to look up full issue information using a condensed identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | The short ID of the issue to resolve. This is a condensed identifier that maps to a specific issue within the organization. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. This determines which organization's namespace to search within. |
No output schema declared.
No examples provided.
search_events_in_table_format Search Events in Table Format ~260
Retrieves a table of events from a specified organization matching your query criteria. Use this to explore event data with selected fields and optional filtering; not intended for full data exports.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | The data source to query. Choose from logs, profile_functions, spans, or uptime_results; available fields vary by dataset. |
| environment | array | – | Filter results to specific environment names. Provide as a comma-separated list or multiple array values. |
| field | array | yes | The columns to include in results. Select up to 20 fields, which can be built-in properties (e.g., transaction, environment), tags in tag[name, type] format, functions like count() or count_if(), or… |
| organization_id_or_slug | string | yes | The organization identifier, either its numeric ID or URL-friendly slug. |
| per_page | integer | – | Maximum number of result rows to return, up to 100 (default is 100). |
| query | string | – | Filter events using Sentry query syntax with logical operators (AND, OR) and field conditions. Example: (transaction:foo AND release:abc) OR (transaction:[bar,baz]). |
No output schema declared.
No examples provided.
submit_user_feedback Submit User Feedback ~181
Submit user feedback for a specific event. This endpoint is deprecated; use the User Feedback Widget or platform-specific User Feedback API instead. Feedback must be submitted within 30 minutes of the event and can be overwritten within 5 minutes of initial submission.
| Name | Type | Req | Description |
|---|---|---|---|
| comments | string | yes | The user's feedback comments or message describing their experience. |
| string | yes | The email address of the user providing feedback. | |
| event_id | string | yes | The unique identifier of the event to attach feedback to. This value can be obtained from the beforeSend callback in your SDK configuration. |
| name | string | yes | The full name of the user providing feedback. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL slug. |
No output schema declared.
No examples provided.
sync_repositories_for_owner Sync Repositories for Owner ~107
Synchronizes repositories from a specified owner with an integrated GitHub organization, ensuring the local repository list matches the current state in GitHub.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. This determines which organization's GitHub integration will be used for the sync operation. |
| owner | string | yes | The GitHub username or organization name that owns the repositories to be synchronized. Only repositories owned by this entity will be synced. |
No output schema declared.
No examples provided.
trigger_issue_autofix Trigger Issue Autofix ~235
Trigger an automated issue fix analysis that identifies root causes, proposes solutions, generates code changes, and optionally creates a pull request. The process runs asynchronously and can be monitored via the GET endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | – | Optional event ID to analyze. If omitted, the system will use the recommended event for the issue. |
| instruction | string | – | Optional custom instruction to guide the autofix analysis and solution generation process. |
| issue_id | integer | yes | The numeric ID of the issue to analyze and fix. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| pr_to_comment_on_url | string | – | Optional URL of a pull request where the autofix should post comments with findings and recommendations. |
| stopping_point | string | – | Optional stopping point for the autofix process. Defaults to root cause analysis if not specified. Valid stages are: root_cause (stop after identifying the cause), solution (stop after proposing a fi… |
No output schema declared.
No examples provided.
update_alert Update Alert ~376
Updates an existing alert configuration including its name, enabled status, trigger conditions, action filters, and connected monitors. This endpoint supports the New Monitors and Alerts system and is currently in beta.
| Name | Type | Req | Description |
|---|---|---|---|
| action_filters | array | – | Array of action filter groups that define conditions and corresponding notification actions. Each filter group contains a logic type, conditions array, and actions array specifying email, Slack, Page… |
| config | object | – | Configuration object specifying the evaluation frequency in minutes. Supported values are 0, 5, 10, 30, 60, 180, 720, or 1440 minutes. |
| detector_ids | array | – | Array of monitor IDs to associate with this alert. Use the organization monitors endpoint to retrieve available monitor IDs. |
| enabled | boolean | – | Whether the alert is active and will evaluate conditions. Defaults to true if not specified. |
| environment | string | – | The environment name where this alert will evaluate conditions. Filters alert evaluation to a specific environment. |
| name | string | yes | The display name for the alert. Must not exceed 256 characters. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| owner | string | – | The owner of the alert, specified as either 'user:USER_ID' or 'team:TEAM_ID' to indicate individual or team ownership. |
| triggers | object | – | Trigger conditions that determine when the alert fires. Supports event-based triggers (first_seen_event, reappeared_event, regression_event, issue_resolved_trigger) with configurable logic type (any-… |
| workflow_id | integer | yes | The numeric ID of the alert to update. |
No output schema declared.
No examples provided.
update_client_key Update Client Key ~310
Update configuration settings for a client key, including its name, activation status, SDK version, and feature flags for replay, performance monitoring, debug mode, feedback, and logs/metrics collection.
| Name | Type | Req | Description |
|---|---|---|---|
| browserSdkVersion | string | – | The Sentry JavaScript SDK version to use with this key. Choose 'latest' for the most recent version or '7.x' for version 7 releases. |
| hasDebug | boolean | – | Enable or disable debug mode to include additional diagnostic information in events sent with this key. |
| hasFeedback | boolean | – | Enable or disable user feedback collection for events sent with this key. |
| hasLogsAndMetrics | boolean | – | Enable or disable logs and metrics collection for events sent with this key. |
| hasPerformance | boolean | – | Enable or disable performance monitoring and transaction tracking for events sent with this key. |
| hasReplay | boolean | – | Enable or disable session replay capture for events sent with this key. |
| isActive | boolean | – | Enable or disable the client key; when deactivated, the key will not accept new events. |
| key_id | string | yes | The unique identifier of the client key to update. |
| name | string | – | A human-readable name for the client key to help identify its purpose or associated application. |
| organization_id_or_slug | string | yes | The ID or slug of the organization that owns the project containing this client key. |
| project_id_or_slug | string | yes | The ID or slug of the project that contains this client key. |
No output schema declared.
No examples provided.
update_data_forwarder Update Data Forwarder ~317
Updates a data forwarder configuration for an organization, or creates/modifies project-specific overrides. Organization-level updates require the full configuration including project IDs, while project-level overrides only need the project ID, overrides object, and enabled status.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Provider-specific configuration object. For SQS: requires queue_url, region, access_key, secret_key (and message_group_id for FIFO queues; s3_bucket is optional). For Segment: requires write_key. For… |
| data_forwarder_id | integer | yes | The numeric ID of the data forwarder to update. |
| enroll_new_projects | boolean | – | Whether newly created projects should automatically be enrolled with this forwarder. Defaults to false if not specified. |
| is_enabled | boolean | – | Whether the data forwarder is active. Defaults to true if not specified. |
| organization_id | integer | yes | The numeric ID of the organization that owns the data forwarder. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the organization slug. |
| project_ids | array | – | Array of project numeric IDs to connect to this forwarder. Projects not included will be unenrolled if previously connected. Required when updating organization-level configuration. |
| provider | string | yes | The data forwarding provider: Segment, Amazon SQS, or Splunk. Each provider requires specific configuration fields. |
No output schema declared.
No examples provided.
update_discover_saved_query Update Discover Saved Query ~397
Modify an existing saved Discover query, including its name, filters, fields, visualization settings, and aggregations.
| Name | Type | Req | Description |
|---|---|---|---|
| display | string | – | Chart visualization type. Choose from: default, previous, top5, daily, dailytop5, or bar. |
| environment | array | – | Array of environment names to filter results by (e.g., 'production', 'staging'). Order is not significant. |
| fields | array | – | Array of fields, functions, or equations to retrieve in query results. Maximum 20 items per request. Supports built-in event properties, tags (prefixed with 'tag['), aggregate functions, and equation… |
| name | string | yes | A user-defined name for the saved query. Maximum 255 characters. |
| orderby | string | – | Field or function name to sort results by. Must be a value from the fields array, excluding equations. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. |
| projects | array | – | Array of project IDs to filter the query results by. Order is not significant. |
| query | string | – | Query filter expression using Sentry's search syntax to narrow results by event properties and tags. |
| query_id | integer | yes | The numeric ID of the saved Discover query to modify. |
| range | string | – | A time range period for the query (e.g., '24h', '7d', '30d'). Determines the lookback window for events. |
| topEvents | integer | – | Number of top events' timeseries to display on the chart. Must be between 1 and 10. |
| yAxis | array | – | Array of aggregate functions to plot on the chart (e.g., 'count()', 'avg(transaction.duration)'). Order determines axis positioning. |
No output schema declared.
No examples provided.
update_external_team Update External Team ~262
Update the configuration of an external team (from GitHub, Slack, Jira, etc.) that is linked to a Sentry team. This allows you to modify the external team's name, provider details, and associated identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | – | The unique identifier or handle for the external team within the provider system (e.g., user ID, team ID, or handle). Optional if not applicable to the provider. |
| external_name | string | yes | The display name or identifier for the external team in the provider system. |
| external_team_id | integer | yes | The unique identifier of the external team object to update, returned when the external team was originally created. |
| integration_id | integer | yes | The numeric ID of the integration that connects Sentry to the external provider. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| provider | string | yes | The external provider platform. Supported providers include GitHub, GitHub Enterprise, Jira Server, Slack, Slack Staging, Perforce, GitLab, Microsoft Teams, and custom SCM systems. |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL slug of the team within the organization. |
No output schema declared.
No examples provided.
update_external_user Update External User ~243
Update the details of an external user account linked to a Sentry user. This synchronizes user information across integrated external providers like GitHub, Slack, Jira, or GitLab.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | – | The user's unique identifier within the external provider system (e.g., user ID, handle, or account number). Optional if already set. |
| external_name | string | yes | The display name or username for this user in the external provider's system. |
| external_user_id | integer | yes | The unique identifier of the external user object to update, returned when the external user was initially created. |
| integration_id | integer | yes | The numeric ID of the integration configuration that connects Sentry to the external provider. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| provider | string | yes | The external provider platform. Supported providers include GitHub, GitHub Enterprise, Jira Server, Slack, Slack Staging, Perforce, GitLab, Microsoft Teams, and custom SCM systems. |
| user_id | integer | yes | The numeric ID of the Sentry user account that this external user is linked to. |
No output schema declared.
No examples provided.
update_inbound_data_filter Update Inbound Data Filter ~200
Enable or disable a specific inbound data filter for a project to control which events are captured and processed. Filters can target browser extensions, localhost traffic, health check transactions, web crawlers, and legacy browser errors.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Set to true to enable the filter or false to disable it. Controls whether the specified filter actively blocks matching events. |
| filter_id | string | yes | The type of inbound filter to update: browser-extensions (blocks extension-caused errors), localhost (blocks 127.0.0.1 and ::1 traffic), filtered-transaction (blocks health checks and pings), web-cra… |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, either as a numeric ID or URL-friendly slug. |
No output schema declared.
No examples provided.
update_issue Update Issue ~257
Modify an issue's attributes such as status, assignment, visibility, and user-specific flags. Only the attributes provided in the request are updated; omitted fields remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | The actor identifier (user ID, username, or team ID) to assign this issue to. Use null or omit to unassign. |
| hasSeen | boolean | – | Mark whether the current user has viewed this issue. Only applicable when the request is made in a user context. |
| isBookmarked | boolean | – | Mark whether the current user has bookmarked this issue. Only applicable when the request is made in a user context. |
| isPublic | boolean | – | Set the issue's visibility to public (true) or private (false). |
| isSubscribed | boolean | – | Subscribe or unsubscribe the current user from workflow notifications for this issue. Only applicable when the request is made in a user context. |
| issue_id | string | yes | The unique identifier of the issue to update. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| status | string | – | The new status for the issue. Must be one of: resolved, resolvedInNextRelease, unresolved, or ignored. |
No output schema declared.
No examples provided.
update_issue_alert_rule Update Issue Alert Rule ~405
Update an issue alert rule that triggers on events matching specified conditions. This operation fully overwrites the alert rule, so all required fields must be provided. Note: This endpoint is deprecated; use the Alert by ID endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| actionMatch | string | yes | Determines how conditions are evaluated: 'all' requires all conditions to be true, 'any' requires at least one to be true, and 'none' requires all to be false. |
| actions | array | yes | An array of actions to execute when conditions and filters are met. Refer to the Create an Issue Alert Rule endpoint for valid action types and structures. |
| conditions | array | yes | An array of trigger conditions that determine when the rule fires. Refer to the Create an Issue Alert Rule endpoint for valid condition types and structures. |
| environment | string | – | Optional environment name to filter alerts by. If specified, the rule only applies to events from this environment. |
| filterMatch | string | – | Determines how filters are evaluated: 'all' requires all filters to match, 'any' requires at least one to match, and 'none' requires all to not match. |
| filters | array | – | An optional array of filters that further refine when the rule fires after conditions are met. Refer to the Create an Issue Alert Rule endpoint for valid filter types and structures. |
| frequency | integer | yes | The interval in minutes between repeated actions for the same issue, ranging from 5 to 43200 minutes (30 days). |
| name | string | yes | A descriptive name for the alert rule, up to 256 characters. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL slug. |
| owner | string | – | Optional identifier of the team or user that owns this alert rule. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or URL slug. |
| rule_id | integer | yes | The numeric ID of the alert rule to update. |
No output schema declared.
No examples provided.
update_issues_bulk Update Issues in Bulk ~361
Bulk update multiple issues by modifying their attributes such as status, assignment, visibility, and user-specific flags. Target issues using the `id` query parameter (repeatable), with optional filtering by current status.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | Assign the issue to a user or team by their actor ID or username. |
| hasSeen | boolean | – | Mark whether the current user has viewed this issue (true) or not (false). Only applicable when invoked with user context. |
| ignoreCount | integer | – | Number of occurrences before an issue is automatically ignored. |
| ignoreDuration | integer | – | Duration in milliseconds for which an ignored issue should remain ignored before auto-resolving. |
| ignoreUserCount | integer | – | Number of unique users affected before an issue is automatically ignored. |
| ignoreUserWindow | integer | – | Time window in milliseconds within which unique user counts are measured for auto-ignore. |
| ignoreWindow | integer | – | Time window in milliseconds within which occurrences are counted for auto-ignore. |
| isBookmarked | boolean | – | Add or remove the issue from the current user's bookmarks (true to bookmark, false to remove). Only applicable when invoked with user context. |
| isPublic | boolean | – | Make the issue publicly visible (true) or restrict to organization members only (false). |
| merge | boolean | – | Merge multiple issues into one (true) or separate a merged issue (false). |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or URL slug. |
| status | string | – | Set the new status for targeted issues. Accepts: resolved, resolvedInNextRelease, unresolved, or ignored. |
No output schema declared.
No examples provided.
update_metric_alert_rule Update Metric Alert Rule ~643
Update a metric alert rule configuration that defines conditions for triggering alerts based on metrics like error count, latency, or failure rate. Warning: This operation fully overwrites the specified metric alert rule. (Deprecated: use Update a Monitor by ID or Update an Alert by ID instead)
| Name | Type | Req | Description |
|---|---|---|---|
| aggregate | string | yes | The aggregate function to apply to the metric. Valid options are: count, count_unique, percentage, avg, apdex, failure_rate, p50, p75, p95, p99, p100, or percentile. |
| alert_rule_id | integer | yes | The numeric ID of the alert rule to update. |
| comparisonDelta | integer | – | Optional time delta in minutes for percentage change comparisons. Required when using a percentage change threshold (e.g., 'x% higher than 60 minutes ago'). Not supported for Crash Free Session/User… |
| dataset | string | – | The dataset to query: events, transactions, metrics, sessions, or generic-metrics. Defaults to events. |
| environment | string | – | Optional environment name to filter events by (e.g., 'production', 'staging'). Defaults to all environments if not specified. |
| eventTypes | array | – | Optional list of event types to monitor: default (Capture Message events), error, or transaction. |
| name | string | yes | A descriptive name for the alert rule, up to 256 characters. |
| organization_id_or_slug | string | yes | The ID or slug of the organization that owns the alert rule. |
| owner | string | – | Optional ID of the team or user that owns this alert rule. |
| projects | array | yes | A list of project names to monitor. The alert will only apply to events from these projects. |
| query | string | yes | An event search query to filter which events trigger the alert (e.g., 'http.status_code:400'). Use an empty string to monitor all events without filtering. |
| queryType | integer | – | The query type: 0 for error events, 1 for transactions, or 2 for none. Defaults based on the specified dataset if not provided. |
| resolveThreshold | number | – | Optional threshold value at which the alert resolves. If not provided, it is automatically set based on the lowest severity trigger's threshold. Must be greater than the critical threshold when thres… |
| thresholdType | integer | yes | The comparison operator for thresholds: 0 for 'Above' or 1 for 'Below'. The resolved threshold operator is automatically set to the opposite. |
| timeWindow | integer | yes | The time window over which to aggregate the metric. Valid options are: 1 minute, 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, or 24 hours. |
| triggers | array | yes | A list of trigger objects, each with a label (critical or warning), alertThreshold value, and actions array. At least one critical trigger is required. Actions specify how to notify (email, Slack, Pa… |
No output schema declared.
No examples provided.
update_monitor Update Monitor ~305
Update an existing monitor's configuration, status, ownership, and notification settings. Changes to the slug will require updates to any instrumented check-in calls referencing the monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | The monitor's configuration object defining its behavior, check intervals, and alert thresholds. |
| is_muted | boolean | – | When enabled, prevents the creation of new monitor incidents while keeping the monitor active for check-ins. |
| monitor_id_or_slug | string | yes | The monitor identifier, either the numeric ID or the monitor slug. |
| name | string | yes | A descriptive name for the monitor used in notifications and UI display. Maximum 128 characters. If not provided, the slug will be derived from this name. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the organization slug. |
| owner | string | – | The team or user responsible for the monitor, specified as 'user:{user_id}' or 'team:{team_id}'. |
| project | string | yes | The slug of the project to associate with this monitor. |
| slug | string | – | A unique identifier for the monitor within the organization. Must contain only lowercase letters, numbers, hyphens, and underscores, and cannot be purely numeric. Maximum 50 characters. Changing this… |
| status | string | – | The operational status of the monitor. Disabled monitors will not process events and do not count toward your monitor quota. Defaults to active. |
No output schema declared.
No examples provided.
update_monitor_detector Update Monitor Detector ~439
Update an existing metric monitor with new configuration, data sources, detection rules, and alert connections. This beta endpoint supports threshold-based, change-based, and dynamic anomaly detection monitors.
| Name | Type | Req | Description |
|---|---|---|---|
| condition_group | object | – | Condition group defining alert triggers and priority levels. Specify logic type, conditions with comparison operators (gt, lte, anomaly_detection), threshold values, and resulting issue states (75=hi… |
| config | object | – | Detection algorithm configuration. Choose `static` for threshold-based alerts, `percent` for change-based detection (requires comparisonDelta in minutes), or `dynamic` for anomaly detection. |
| data_sources | array | – | Array of data source configurations defining what metric to measure. Each source specifies the aggregate function (e.g., count(), p95(span.duration)), dataset (events, events_analytics_platform, or g… |
| description | string | – | Detailed description of the monitor's purpose and scope. Will be included in generated issues. |
| detector_id | integer | yes | The numeric ID of the monitor to update. |
| enabled | boolean | – | Boolean flag to enable or disable the monitor. Set to false to deactivate without deleting. |
| name | string | yes | Display name for the monitor. Maximum 200 characters. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL-friendly slug. |
| owner | string | – | Owner assignment as either a user ID (prefixed with 'user:') or team ID (prefixed with 'team:'). Example: 'user:123456' or 'team:456789'. |
| type | string | yes | The monitor classification type. Currently supports `metric_issue` for metric-based monitoring. |
| workflow_ids | array | – | Array of alert workflow IDs to connect this monitor to. Use the Fetch Alerts endpoint to discover available workflow IDs. |
No output schema declared.
No examples provided.
update_monitor_project Update Monitor ~325
Update an existing monitor's configuration, name, status, and ownership settings. Changes to the monitor slug will require updates to any instrumented check-in calls referencing the old slug.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | The monitor's configuration object defining its behavior, thresholds, and check-in expectations. |
| is_muted | boolean | – | When enabled, prevents the creation of new monitor incidents while keeping the monitor active. |
| monitor_id_or_slug | string | yes | The monitor identifier, either the numeric ID or URL-friendly slug. |
| name | string | yes | Display name for the monitor used in notifications and UI. Maximum 128 characters. If not provided, the slug will be auto-derived from this name. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL-friendly slug. |
| owner | string | – | The team or user responsible for this monitor, specified as 'user:{user_id}' or 'team:{team_id}'. |
| project | string | yes | The project slug to associate this monitor with. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or URL-friendly slug. |
| slug | string | – | Unique identifier for the monitor within the organization. Must start with a letter or underscore, contain only lowercase letters, numbers, hyphens, and underscores, and not exceed 50 characters. Cha… |
| status | string | – | Current operational state of the monitor. Disabled monitors will not accept events and do not count toward quota limits. Defaults to active. |
No output schema declared.
No examples provided.
update_organization Update Organization ~922
Update organization settings, membership policies, security configurations, data privacy controls, and integration permissions. Changes apply to all projects within the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| alertsMemberWrite | boolean | – | Grant all members the ability to create, edit, and delete alert rules. |
| allowJoinRequests | boolean | – | Allow users to submit requests to join the organization without requiring an explicit invitation. |
| allowSharedIssues | boolean | – | Allow sharing of limited issue details with anonymous users via public links. |
| attachmentsRole | string | – | Minimum role required to download event attachments such as crash reports and log files: member, admin, manager, or owner. |
| avatar | string | – | Organization avatar image encoded as base64; required when avatarType is set to upload. |
| cancelDeletion | boolean | – | Restore an organization that is currently scheduled for deletion, canceling the deletion process. |
| codecovAccess | boolean | – | Enable Code Coverage Insights for tracking test coverage trends; available only on Team plan and above. |
| dataScrubberDefaults | boolean | – | Apply default data scrubbers organization-wide to prevent sensitive data like passwords and credit card numbers from being stored. |
| debugFilesRole | string | – | Minimum role required to download debug files, ProGuard mappings, and source maps: member, admin, manager, or owner. |
| defaultRole | string | – | Default role assigned to newly invited members: member, admin, manager, or owner. |
| enhancedPrivacy | boolean | – | Enable enhanced privacy mode to minimize personally identifiable information and source code in notifications and exports. |
| eventsMemberAdmin | boolean | – | Grant all members the ability to delete events and use the delete & discard action. |
| githubNudgeInvite | boolean | – | Enable Sentry to detect GitHub repository committers not yet in the organization and suggest invitations; requires GitHub integration. |
| githubPRBot | boolean | – | Enable Sentry to post comments on recent GitHub pull requests suspected of introducing issues; requires GitHub integration. |
| gitlabPRBot | boolean | – | Enable Sentry to post comments on recent GitLab merge requests suspected of introducing issues; requires GitLab integration. |
| hasGranularReplayPermissions | boolean | – | Enable per-member access control for session replay data instead of role-based access. |
| hideAiFeatures | boolean | – | Hide AI-powered features and recommendations from the organization's interface. |
| isEarlyAdopter | boolean | – | Enable early access to unreleased features and experimental functionality. |
| issueAlertsThreadFlag | boolean | – | Allow Sentry Slack integration to post Issue Alert notifications as threaded replies instead of standalone messages; requires Slack integration. |
| metricAlertsThreadFlag | boolean | – | Allow Sentry Slack integration to post Metric Alert notifications as threaded replies instead of standalone messages; requires Slack integration. |
| name | string | – | New display name for the organization; limited to 64 characters. |
| openMembership | boolean | – | Allow organization members to join any team without explicit invitation. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| relayPiiConfig | string | – | Advanced data scrubbing rules as a JSON string for masking or removing sensitive data patterns; overwrites existing rules and applies only to new events. See documentation for rule syntax and example… |
| replayAccessMembers | array | – | List of user IDs granted access to replay data; only enforced when granular replay permissions are enabled. |
| require2FA | boolean | – | Require and enforce two-factor authentication for all organization members. |
| safeFields | array | – | List of field names that data scrubbers should explicitly ignore and not redact. |
| scrapeJavaScript | boolean | – | Allow Sentry to automatically fetch missing JavaScript source context from public CDNs when available. |
| scrubIPAddresses | boolean | – | Prevent IP addresses from being stored in new events across all projects. |
| sensitiveFields | array | – | List of additional field names to scrub across all projects; matched against event data during processing. |
| slug | string | – | New organization slug for URLs; must be unique across the instance and not exceed 50 characters. |
| storeCrashReports | integer | – | Number of native crash reports (minidumps, etc.) to retain per issue: 0 (disabled), 1, 5, 10, 20, 50, 100, or -1 (unlimited). |
| trustedRelays | array | – | List of local Relay instances registered for the organization, each containing name, public key, and description; available only on Business and Enterprise plans. |
No output schema declared.
No examples provided.
update_organization_alerts_bulk Update Organization Alerts in Bulk ~115
Bulk enable or disable alerts across an organization, optionally filtered by search query. This beta endpoint supports the New Monitors and Alerts system.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | Set to true to enable the selected alerts, or false to disable them. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| query | string | – | Optional search query to filter which alerts are affected by this operation. If omitted, the operation applies to all alerts in the organization. |
No output schema declared.
No examples provided.
update_organization_dashboard Update Organization Dashboard ~268
Update an organization's custom dashboard configuration, including its title, widgets, filters, and display settings. Supports bulk edits to widget arrangements, queries, fields, and display types.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard_id | integer | yes | The numeric ID of the dashboard to update. |
| environment | array | – | An array of environment names to filter the dashboard's data scope. Only events from these environments will be displayed. |
| filters | object | – | An object containing saved filter criteria applied across the dashboard. Filters are applied to all widgets unless overridden at the widget level. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| permissions | object | – | Access control settings that define which users can view or edit this dashboard. |
| projects | array | – | An array of project identifiers to filter the dashboard's data scope. Only events from these projects will be displayed. |
| title | string | – | The dashboard's display name. Must not exceed 255 characters. |
| utc | boolean | – | When enabled, displays all saved time ranges and timestamps in UTC timezone instead of the user's local timezone. |
| widgets | array | – | An ordered array of widget objects representing the dashboard's visualizations. Each widget can include query definitions, field selections, and display type configurations. |
No output schema declared.
No examples provided.
update_organization_member_roles Update Organization Member Roles ~204
Update an organization member's roles at both the organization and team levels. Requires user auth tokens and enforces permission hierarchy—you can only assign roles with equal or lower permissions than your own.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The numeric ID of the member whose roles should be updated. |
| orgRole | string | – | The organization-level role to assign. Options range from billing (payment/compliance only) through member, manager, and owner (unrestricted access). The admin role is deprecated for Business and Ent… |
| organization_id_or_slug | string | yes | The organization identifier, either its numeric ID or URL slug. |
| teamRoles | array | – | Array of team-level role assignments. Each entry specifies a team (by slug) and assigns either contributor (view and act on issues) or admin (full team management) role. Order is not significant. Omi… |
No output schema declared.
No examples provided.
update_organization_member_team_role Update Organization Member Team Role ~170
Update an organization member's role within a specific team. The member must already be part of the team. Note that organization admins, managers, and owners automatically receive a minimum team role of admin on all their teams.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The numeric ID of the organization member whose team role should be updated. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. |
| teamRole | string | – | The team-level role to assign. Choose 'contributor' for view and event action permissions, or 'admin' for full team management including project and membership control. Defaults to 'contributor' if n… |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL slug. |
No output schema declared.
No examples provided.
update_organization_monitors_enabled_state Update Organization Monitors Enabled State ~138
Bulk enable or disable monitors across an organization, optionally filtered by search criteria. This beta endpoint supports the New Monitors and Alerts system.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | Set to true to enable the selected monitors or false to disable them. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the organization slug. |
| query | string | – | Optional search query to filter which monitors are affected. Supports filtering by monitor name, type (such as error, metric_issue, or issue_stream), or assignee (email, username, team reference with… |
No output schema declared.
No examples provided.
update_organization_release Update Organization Release ~209
Update release metadata including repository references, deployment URL, and release date. Allows modification of commit information, external links, and timing details for an existing release.
| Name | Type | Req | Description |
|---|---|---|---|
| dateReleased | string | – | An ISO 8601 formatted date-time indicating when the release was deployed to production. If omitted, the current server time is used. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| refs | array | – | An array of commit references for each repository in the release. Each entry must include the repository identifier and commit SHA (HEAD). Optionally include the previous commit SHA if this is the fi… |
| url | string | – | A URI pointing to the release, such as a GitHub repository URL or deployment interface. Must be a valid URI format. |
| version | string | yes | The semantic version string that uniquely identifies the release within the organization. |
No output schema declared.
No examples provided.
update_organization_release_file Update Organization Release File ~117
Update metadata for a file associated with an organization release, such as its name or distribution identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| dist | string | – | The new distribution name to associate with the file. |
| file_id | string | yes | The unique identifier of the file to update. |
| name | string | – | The new full file path or name for the release file. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| version | string | yes | The version string that identifies the release. |
No output schema declared.
No examples provided.
update_project Update Project ~339
Update project settings, metadata, and configuration options. Most settings require elevated permissions; only bookmarking and preprod-related automation settings can be modified with basic project:read access.
| Name | Type | Req | Description |
|---|---|---|---|
| isBookmarked | boolean | – | Star or unstar the project in the projects tab. Updatable with project:read permission. |
| name | string | – | The display name for the project. Must not exceed 200 characters. |
| organization_id_or_slug | string | yes | The organization identifier, either its numeric ID or URL-friendly slug. |
| platform | string | – | The platform or technology stack associated with the project (e.g., 'javascript', 'python', 'java'). |
| project_id_or_slug | string | yes | The project identifier, either its numeric ID or URL-friendly slug. |
| resolveAge | integer | – | Hours of inactivity after which issues are automatically resolved. Set to 0 to disable auto-resolution. |
| scmSourceContextEnabled | boolean | – | Enable automatic source context retrieval from configured SCM integrations to enrich stack traces with code snippets. |
| slug | string | – | A URL-friendly identifier for the project used in the interface. Must be 1-100 characters, contain only lowercase letters, numbers, hyphens, and underscores, and cannot be purely numeric. |
| subjectPrefix | string | – | A custom prefix prepended to email subjects for alerts from this project. Must not exceed 200 characters. |
| subjectTemplate | string | – | The email subject template for individual alerts, supporting variables like $title, $shortID, $projectID, $orgID, and tag references (e.g., ${tag:environment}). Must not exceed 200 characters. |
No output schema declared.
No examples provided.
update_project_environment_visibility Update Project Environment Visibility ~136
Update the visibility status of a project environment, allowing you to show or hide it from the project's environment list.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | The name of the environment to update (e.g., 'production', 'staging', 'development'). |
| isHidden | boolean | yes | Set to `true` to make the environment visible, or `false` to hide it from the project's environment list. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
update_project_ownership_configuration Update Project Ownership Configuration ~232
Updates ownership configurations for a project, including rules, fallthrough behavior, auto-assignment settings, and CODEOWNERS synchronization. Only submitted attributes are modified.
| Name | Type | Req | Description |
|---|---|---|---|
| autoAssignment | string | – | Configures automatic issue assignment behavior. Choose from: auto-assign to the issue creator, auto-assign based on suspect commits from version control, or disable auto-assignment entirely. |
| codeownersAutoSync | boolean | – | When enabled, automatically syncs issue owners with updates to the CODEOWNERS file in releases. Defaults to true. |
| fallthrough | boolean | – | Determines ownership assignment when no ownership rule matches. When true, all project members become owners; when false, no owners are assigned for unmatched cases. |
| organization_id_or_slug | string | yes | The ID or slug of the organization that owns the project. |
| project_id_or_slug | string | yes | The ID or slug of the project whose ownership configuration will be updated. |
| raw | string | – | Raw ownership rules configuration in the format specified by the Ownership Rules documentation. This defines which team members or groups own specific code paths or issue types. |
No output schema declared.
No examples provided.
update_project_symbol_source Update Project Symbol Source ~603
Update an existing custom symbol source configuration in a project. Modify source type, layout, authentication credentials, and file filtering rules for symbol resolution.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | – | The AWS Access Key for S3 authentication. Required for S3 sources; invalid for HTTP and GCS sources. |
| bucket | string | – | The bucket name in Google Cloud Storage or Amazon S3. Required for GCS and S3 sources; invalid for HTTP sources. |
| casing | string | yes | Path casing normalization rule: lowercase, uppercase, or default (no transformation). |
| client_email | string | – | The service account email address for GCS authentication. Required for GCS sources; invalid for HTTP and S3 sources. |
| filetypes | array | – | Array of file type extensions to enable for symbol resolution (e.g., 'pdb', 'dwarf', 'macho'). Order is not significant. |
| id | string | – | Custom internal identifier for the source. Must be unique across all sources in the project and cannot begin with 'sentry:'. If omitted, a UUID will be automatically generated. |
| layoutType | string | yes | The directory structure layout format used by the symbol source: native, symstore, symstore_index2, ssqp, unified, debuginfod, or slashsymbols. |
| name | string | yes | A human-readable display name for the symbol source. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL-friendly slug. |
| password | string | – | Password for HTTP Basic Authentication. Valid only for HTTP sources. |
| path_patterns | array | – | Array of glob patterns to filter which debug and code file paths are queried from this source. Order is not significant. |
| prefix | string | – | The object key prefix path within the GCS or S3 bucket. Optional for cloud storage sources; invalid for HTTP sources. |
| private_key | string | – | The private key for GCS service account authentication. Required for GCS sources when not using impersonated tokens; invalid for HTTP and S3 sources. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or URL-friendly slug. |
| region | string | – | The AWS region where the S3 bucket is located. Required for S3 sources; invalid for HTTP and GCS sources. |
| requires_checksum | boolean | – | Whether symbol lookups from this source must include and validate debug checksums. |
| secret_key | string | – | The AWS Secret Access Key for S3 authentication. Required for S3 sources; invalid for HTTP and GCS sources. |
| type | string | yes | The symbol source backend type: HTTP (SymbolServer), Google Cloud Storage, or Amazon S3. |
| url | string | – | The base URL of the HTTP symbol server. Required only for HTTP sources; invalid for cloud storage sources. |
| username | string | – | Username for HTTP Basic Authentication. Valid only for HTTP sources. |
No output schema declared.
No examples provided.
update_release_file Update Release File ~137
Update metadata for a specific file within a project release, such as its name or distribution identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| dist | string | – | The new distribution name to associate with the file. |
| file_id | string | yes | The unique identifier of the file to update. |
| name | string | – | The new full file path or name for the release file. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, either as a numeric ID or URL-friendly slug. |
| version | string | yes | The release version identifier to target. |
No output schema declared.
No examples provided.
update_service_hook Update Service Hook ~149
Update an existing service hook configuration for a project, including its webhook URL and subscribed event types.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | An array of event types to subscribe to. The hook will trigger for each specified event. Order is not significant. |
| hook_id | string | yes | The unique identifier (GUID) of the service hook to update. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL-friendly slug. |
| url | string | yes | The destination URL where webhook payloads will be sent. Must be a valid HTTP or HTTPS endpoint. |
No output schema declared.
No examples provided.
What is the com.mcparmory/sentry MCP server?
com.mcparmory/sentry is an MCP server listed in the public MCP registry as com.mcparmory/sentry. Track errors, manage performance alerts, and configure dashboards and monitors. This page covers its container image (ghcr.io/mcparmory/sentry:1.0.2).
Is the com.mcparmory/sentry MCP server safe to use?
com.mcparmory/sentry scores 48 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/sentry MCP server expose?
com.mcparmory/sentry exposes 200 tools: list_organizations, get_organization, update_organization, update_metric_alert_rule, list_integration_providers, and 195 more. Their descriptions and schemas cost roughly 33,368 tokens of context every time the server is loaded.
Is the com.mcparmory/sentry MCP server still maintained?
com.mcparmory/sentry is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.