com.mcparmory/sentry
PYPI · MCPARMORY-SENTRY · 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 Security87
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
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: the license (MIT License) isn't a recognized OSI-approved license. 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 Management87
- Stability observed for 26 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 current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/sentry MCP server?
com.mcparmory/sentry runs locally as a PyPI package, launched with uvx mcparmory-sentry. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-sentry
claude mcp add com-mcparmory-sentry -- uvx mcparmory-sentry
{
"mcpServers": {
"com-mcparmory-sentry": {
"command": "uvx",
"args": [
"mcparmory-sentry"
]
}
}
} {
"servers": {
"com-mcparmory-sentry": {
"command": "uvx",
"args": [
"mcparmory-sentry"
]
}
}
} codex mcp add com-mcparmory-sentry -- uvx mcparmory-sentry
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-sentry": {
"type": "local",
"command": [
"uvx",
"mcparmory-sentry"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-sentry --command uvx --arg mcparmory-sentry
mcp_servers:
com-mcparmory-sentry:
command: "uvx"
args: ["mcparmory-sentry"] {
"McpServers": {
"com-mcparmory-sentry": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-sentry"
]
}
}
} assistant mcp add com-mcparmory-sentry -t stdio -c uvx -a mcparmory-sentry
{
"mcpServers": {
"com-mcparmory-sentry": {
"command": "uvx",
"args": [
"mcparmory-sentry"
]
}
}
} 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.
- 20 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 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 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
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 pypi/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 | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_member_to_organization Add Member to Organization ~240
Add or invite a member to an organization with optional role assignment and team membership. Sends an email invitation by default unless disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address of the member to invite. Must be a valid email format with a maximum length of 75 characters. | |
| orgRole | string | – | Organization-level role for the new member. Options range from `member` (view and act on events) to `owner` (unrestricted access). Defaults to `member`. Note: `admin` role is deprecated for Business… |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL-friendly slug. |
| reinvite | boolean | – | Whether to re-invite a member who has already received an invitation to the organization. Defaults to true. |
| sendInvite | boolean | – | Whether to send an email invitation notification to the member. Defaults to true. |
| teamRoles | array | – | Array of team assignments with associated roles. Each entry assigns the member to a team with either `contributor` (view and act on issues) or `admin` (full team management) permissions. |
No output schema declared.
No examples provided.
add_member_to_team Add Member to Team ~159
Add an organization member to a team. The operation returns different success codes based on context: 201 if successfully added, 202 if an access request is generated (pending approval), or 204 if the member is already on the team. Permission requirements vary based on the organization's 'Open Membership' setting and token type.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The numeric ID of the organization member to add to the team. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. Used to scope the operation to a specific organization. |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL slug. Identifies which team the member should be added to. |
No output schema declared.
No examples provided.
add_symbol_source_to_project Add Symbol Source to Project ~580
Add a custom symbol source to a project for debug symbol resolution. Supports HTTP, Google Cloud Storage, and Amazon S3 backends with configurable layout types and casing rules.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | – | The AWS Access Key for S3 authentication. Required for S3 sources; must be omitted for HTTP and GCS sources. |
| bucket | string | – | The bucket name containing symbols. Required for GCS and S3 sources; must be omitted for HTTP sources. |
| casing | string | yes | How file paths are normalized: lowercase, uppercase, or default (no transformation). |
| client_email | string | – | The service account email address for GCS authentication. Required for GCS sources; must be omitted for HTTP and S3 sources. |
| filetypes | array | – | Array of file extensions to enable for this source (e.g., 'pdb', 'elf', 'dwarf'). If omitted, all supported types are enabled. |
| layoutType | string | yes | The directory layout format used by the symbol source: native, symstore, symstore_index2, SSQP, unified, debuginfod, or /symbols. |
| name | string | yes | A human-readable display name for this 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 match against debug and code file paths. If omitted, all paths are accepted. |
| prefix | string | – | A path prefix within the bucket to scope symbol lookups. Optional for GCS and S3 sources; must be omitted for HTTP sources. |
| private_key | string | – | The private key for GCS service account authentication. Required for GCS sources unless using impersonated tokens; must be omitted 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; must be omitted for HTTP and GCS sources. |
| requires_checksum | boolean | – | Whether debug checksums must be present and validated for files from this source. |
| secret_key | string | – | The AWS Secret Access Key for S3 authentication. Required for S3 sources; must be omitted 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 symbol server. Required for HTTP sources; must be omitted for GCS and S3 sources. |
| username | string | – | Username for HTTP Basic Authentication. Valid only for HTTP sources. |
No output schema declared.
No examples provided.
add_team_to_project Add Team to Project ~121
Grant a team access to a project, enabling collaboration and resource sharing within the specified 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 within 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 to grant access. |
No output schema declared.
No examples provided.
bulk_update_issues Bulk Update Issues ~516
Bulk update attributes on up to 1000 issues in an organization. Use the `id` query parameter for non-status updates, or omit it for status updates to match issues by filter criteria. Issues out of scope are silently skipped; returns HTTP 204 if no issues match.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | yes | Assign the issues to a user or team. Specify as `<user_id>`, `user:<user_id>`, `<username>`, `<user_primary_email>`, or `team:<team_id>`. |
| discard | boolean | yes | Discard the selected issues instead of updating them when set to true. |
| environment | array | – | Filter issues by one or more environment names. Specify as an array of environment identifiers. |
| hasSeen | boolean | yes | Mark the issue as seen by the requesting user when set to true. |
| inbox | boolean | yes | Mark the issue as reviewed by the requesting user when set to true. |
| isBookmarked | boolean | yes | Bookmark the issue for the requesting user when set to true. |
| isPublic | boolean | yes | Publish the issue to make it publicly visible when set to true. |
| isSubscribed | boolean | yes | Subscribe the requesting user to the issue when set to true. |
| limit | integer | – | Maximum number of issues to update, up to 100. Defaults to 100. |
| merge | boolean | yes | Merge the selected issues together when set to true. |
| organization_id_or_slug | string | yes | The organization identifier, either its numeric ID or URL slug. |
| priority | string | yes | Set the priority level for the issues: `low`, `medium`, or `high`. |
| query | string | – | Search query to filter issues (e.g., `is:unresolved`). Defaults to `is:unresolved` if not provided; use an empty string to include all results. |
| status | string | yes | Limit mutations to issues with this status: `resolved`, `unresolved`, `ignored`, `resolvedInNextRelease`, or `muted`. |
| statusDetails | object | yes | Additional context for the status change, such as release information for resolution details. Release-based updates are restricted to issues within a single project. |
| substatus | string | – | Set the issue substatus to one of: `archived_until_escalating`, `archived_until_condition_met`, `archived_forever`, `escalating`, `ongoing`, `regressed`, or `new`. Omit or set to null to leave unchan… |
No output schema declared.
No examples provided.
create_alert_for_organization Create Alert for Organization ~393
Creates a new alert for an organization to monitor issues and trigger notifications based on specified conditions. This endpoint is currently in beta and supports the New Monitors and Alerts system.
| Name | Type | Req | Description |
|---|---|---|---|
| action_filters | array | – | Array of action filter groups that define conditions and corresponding actions to execute. Each filter group contains a logic type, conditions array (supporting age, assignment, category, frequency,… |
| config | object | – | Configuration object specifying the evaluation frequency in minutes. Supported values are 0, 5, 10, 30, 60, 180, 720, or 1440 minutes (up to 24 hours). |
| detector_ids | array | – | Array of monitor IDs to associate with this alert. Use the Fetch Organization Monitors endpoint to retrieve available monitor IDs. |
| enabled | boolean | – | Whether the alert is active and will evaluate conditions. Defaults to enabled if not specified. |
| environment | string | – | The environment name where the alert will evaluate conditions, such as 'production' or 'staging'. |
| name | string | yes | A descriptive name for the alert, up to 256 characters in length. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| owner | string | – | The user or team who owns this alert, specified as 'user:USER_ID' or 'team:TEAM_ID'. |
| triggers | object | – | Trigger conditions that determine when the alert fires. Includes organization ID, logic type (any-short, all, or none), an array of condition objects (first_seen_event, issue_resolved_trigger, reappe… |
No output schema declared.
No examples provided.
create_dashboard Create Dashboard ~244
Create a new dashboard for an organization to visualize and monitor project metrics, events, and custom data. Dashboards can include widgets, project filters, environment filters, and saved search criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | A list of environment names to filter dashboard data to specific environments. |
| filters | object | – | A structured object containing saved search filters and query parameters applied to the dashboard. |
| is_favorited | boolean | – | When set to true, automatically adds this dashboard to the requesting user's favorites list. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| permissions | object | – | Access control settings that determine which users can view and edit this dashboard. |
| projects | array | – | A list of project identifiers to filter dashboard data to specific projects. |
| title | string | yes | A human-readable name for the dashboard. Limited to 255 characters. |
| utc | boolean | – | When enabled, displays all time ranges and timestamps on the dashboard in UTC timezone instead of the user's local timezone. |
| widgets | array | – | An ordered list of widget objects that define the visualizations and data displayed on the dashboard. |
No output schema declared.
No examples provided.
create_data_forwarder_for_organization Create Data Forwarder for Organization ~267
Creates a new data forwarder for an organization to forward data to external providers like Segment, Amazon SQS, or Splunk. Only one data forwarder per provider is allowed per organization.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Provider-specific configuration object. For SQS: queue_url, region, access_key, secret_key (required), plus optional message_group_id for FIFO queues and optional s3_bucket. For Segment: write_key (r… |
| enroll_new_projects | boolean | – | Whether newly created projects are automatically enrolled with this data forwarder. Defaults to disabled. |
| is_enabled | boolean | – | Whether the data forwarder is active and forwarding data. Defaults to enabled. |
| organization_id | integer | yes | The numeric ID of the organization that will own this data forwarder. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the organization slug. |
| project_ids | array | – | List of project IDs to enroll with this data forwarder. Projects not included will be unenrolled if they were previously connected. |
| provider | string | yes | The data destination provider: Segment, Amazon SQS, or Splunk. Each provider requires specific configuration keys. |
No output schema declared.
No examples provided.
create_deploy_for_release Create Deploy for Release ~233
Create a deployment record for a specific release version to a target environment. This tracks when and where a release was deployed, optionally linking it to specific projects.
| Name | Type | Req | Description |
|---|---|---|---|
| dateFinished | string | – | The timestamp when the deployment completed, in ISO 8601 format. Defaults to the current time if not provided. |
| dateStarted | string | – | The timestamp when the deployment began, in ISO 8601 format. |
| environment | string | yes | The target environment for this deployment (e.g., production, staging, development). Limited to 64 characters. |
| name | string | – | A human-readable name for this deployment. Limited to 64 characters. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| projects | array | – | A list of project slugs to associate with this deployment. If omitted, the deployment applies to all projects in the release. |
| url | string | – | A URL pointing to deployment details, logs, or related resources. Must be a valid URI. |
| version | string | yes | The release version identifier to deploy. |
No output schema declared.
No examples provided.
create_metric_monitor_for_project Create Metric Monitor for Project ~491
Create a metric-based monitor for a project to detect issues based on error counts, performance metrics, or custom measurements. This beta endpoint supports multiple monitor types including threshold-based, change-based, and dynamic anomaly detection.
| Name | Type | Req | Description |
|---|---|---|---|
| condition_group | object | – | Condition group defining when to trigger issue creation and priority assignment. Specify logic type, comparison operators (gt, lte, anomaly_detection), thresholds, and result states (75=high priority… |
| config | object | – | Detection algorithm configuration. Choose `static` for threshold-based alerts, `percent` for change-based detection (requires comparisonDelta in minutes: 300, 900, 3600, 86400, 604800, or 2592000), o… |
| 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 | – | Optional descriptive text about the monitor's purpose. This text will be included in any resulting issues created by the monitor. |
| enabled | boolean | – | Set to `false` to create the monitor in a disabled state. Defaults to `true` (enabled). |
| name | string | yes | A descriptive name for the monitor. Maximum 200 characters. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL slug. |
| owner | string | – | The owner of this monitor, specified as either a user ID (format: `user:123456`) or team ID (format: `team:456789`). |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or URL slug. |
| type | string | yes | The monitor classification type. Currently supports `metric_issue` for metric-based monitoring. |
| workflow_ids | array | – | Optional array of alert workflow IDs to automatically connect this monitor to existing alerts. Use the Fetch Alerts endpoint to discover available workflow IDs. |
No output schema declared.
No examples provided.
create_monitor Create Monitor ~290
Create a new monitor for uptime or performance tracking within an organization. The monitor will be associated with a specific project and can be configured with custom check-in rules and notification settings.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | The monitor configuration object that defines check-in rules, thresholds, and behavior. |
| is_muted | boolean | – | When enabled, prevents the creation of monitor incidents even when check-in failures occur. |
| name | string | yes | A human-readable name for the monitor (up to 128 characters) used in notifications. If no slug is provided, it will be automatically derived from this name. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| owner | string | – | The team or user responsible for the monitor, specified as 'user:{user_id}' or 'team:{team_id}'. |
| project | string | yes | The project slug that this monitor will be associated with. |
| slug | string | – | A unique identifier for the monitor within the organization (up to 50 characters). Must start with a letter or underscore and contain only lowercase letters, numbers, hyphens, and underscores. Requir… |
| status | string | – | The operational status of the monitor. Active monitors accept events and count toward quota; disabled monitors do not. Defaults to active. |
No output schema declared.
No examples provided.
create_or_update_external_issue Create or Update External Issue ~196
Create or update an external issue linked to a Sentry issue through an integration platform installation. This establishes a bidirectional link between a Sentry issue and an external service's issue tracker.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | A unique identifier for the external issue within the external service (e.g., issue number, ticket ID, or key). This is used to prevent duplicate creations and to identify the issue for updates. |
| issueId | integer | yes | The numeric ID of the Sentry issue to link with the external issue. |
| project | string | yes | The project identifier or key in the external service where the issue exists or will be created. |
| uuid | string | yes | The unique identifier of the integration platform installation that will handle the external issue creation or update. |
| webUrl | string | yes | The full URL of the external issue in the integrated service (e.g., the direct link to the issue in the external tracker). |
No output schema declared.
No examples provided.
create_organization_member Create Organization Member ~164
Provision a new organization member via SCIM protocol. The member will be assigned the organization's default role unless a specific role is provided.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL-friendly slug. |
| sentryOrgRole | string | – | The organization role to assign the member. Determines permissions for billing management, event handling, team/project administration, and global integrations. Defaults to the organization's default… |
| userName | string | yes | The email address for the new member, used as the SAML identifier. Must be a valid email format. |
No output schema declared.
No examples provided.
create_project_client_key Create Project Client Key ~170
Generate a new client key for a project with server-generated secret and public key credentials. Use this to create authentication keys for integrating with the project.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A human-readable name for the key (up to 64 characters). If omitted, the server will auto-generate a name. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or URL-friendly slug. |
| useCase | string | – | The intended use case for this key: `user` for standard client integration, `profiling` for performance profiling, `tempest` for testing, or `demo` for demonstration purposes. Defaults to `user` if n… |
No output schema declared.
No examples provided.
create_project_for_team Create Project for Team ~216
Create a new project within a team. Requires org:write or team:admin scope if your organization has disabled member project creation.
| Name | Type | Req | Description |
|---|---|---|---|
| default_rules | boolean | – | Whether to enable default alert rules that notify on every new issue. Defaults to true; set to false to require manual alert configuration. |
| name | string | yes | The display name for the project. Must not exceed 50 characters. |
| organization_id_or_slug | string | yes | The organization identifier, either its numeric ID or URL slug. |
| platform | string | – | The platform or technology stack associated with the project (e.g., JavaScript, Python, Java). |
| slug | string | – | A URL-safe identifier for the project used in the interface. If omitted, it will be auto-generated from the project name. Must contain only lowercase letters, numbers, hyphens, and underscores, canno… |
| team_id_or_slug | string | yes | The team identifier, either its numeric ID or URL slug. |
No output schema declared.
No examples provided.
create_release_for_organization Create Release for Organization ~271
Create a new release for an organization to enable Sentry's error reporting, source map uploads, and debug features. Releases correlate first-seen events with the code version that introduced issues.
| Name | Type | Req | Description |
|---|---|---|---|
| dateReleased | string | – | An optional timestamp indicating when the release was deployed to production. If omitted, the current time is used. Must be in ISO 8601 date-time format. |
| organization_id_or_slug | string | yes | The organization identifier, either a numeric ID or URL-friendly slug. |
| projects | array | yes | A list of project slugs associated with this release. Order is not significant. Each item should be a valid project slug string. |
| refs | array | – | An optional array of commit references for repositories included in this release. Each reference should include `repository` and `commit` (the HEAD SHA), and may optionally include `previousCommit` (… |
| url | string | – | An optional URL pointing to the release, such as a link to the source code repository or release notes page. |
| version | string | yes | A unique version identifier for this release, such as a semantic version number, commit hash, or other build identifier. |
No output schema declared.
No examples provided.
create_replay_deletion_job Create Replay Deletion Job ~215
Create a new batch job to delete replays matching specified criteria. The job will process replays within the given time range, environments, and query filters.
| Name | Type | Req | Description |
|---|---|---|---|
| environments | array | yes | A list of environment names to filter replays for deletion. Only replays from these environments will be included in the job. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL slug of the project. |
| query | string | – | A search query string to further filter which replays should be deleted. The query uses the same syntax as replay search filters. |
| rangeEnd | string | yes | The end of the time range for replay deletion, specified as an ISO 8601 formatted datetime string (inclusive). |
| rangeStart | string | yes | The start of the time range for replay deletion, specified as an ISO 8601 formatted datetime string (inclusive). |
No output schema declared.
No examples provided.
create_saved_query Create Saved Query ~452
Create a new saved query for an organization to store custom Discover search configurations, including filters, fields, aggregations, and visualization settings.
| Name | Type | Req | Description |
|---|---|---|---|
| display | string | – | The chart visualization type: 'default' (line chart), 'previous' (comparison), 'top5' (top 5 series), 'daily' (daily breakdown), 'dailytop5' (daily top 5), or 'bar' (bar chart). |
| environment | array | – | An array of environment names to filter the query by (e.g., 'production', 'staging'). If omitted, all environments are included. |
| fields | array | – | An array of up to 20 fields, functions, or equations to retrieve. Fields can be event properties (e.g., 'transaction'), tags (e.g., 'tag[isEnterprise]'), functions (e.g., 'count_if(transaction.durati… |
| name | string | yes | A descriptive name for the saved query, up to 255 characters. |
| orderby | string | – | The field or function to sort results by. Must be one of the fields specified in the fields array, and cannot be an equation. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. |
| projects | array | – | An array of project IDs to filter the query results by. If omitted, the query applies to all projects in the organization. |
| query | string | – | A search query using Sentry's query syntax to filter results further. Supports boolean operators and field-specific filters. |
| range | string | – | A time range period for the query (e.g., '24h', '7d', '30d'). Defines the default time window when the saved query is loaded. |
| topEvents | integer | – | The number of top events' time-series to display on the chart, between 1 and 10. Only applies when using top-events visualization modes. |
| yAxis | array | – | An array of aggregate functions to plot on the chart (e.g., 'count()', 'avg(transaction.duration)'). Used for time-series visualization. |
No output schema declared.
No examples provided.
create_team Create Team ~107
Create a new team within an organization. At least one of `name` or `slug` must be provided in the request body.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either its numeric ID or URL-friendly slug. |
| slug | string | – | A URL-friendly identifier for the team (lowercase alphanumeric characters, hyphens, and underscores; cannot be purely numeric). Maximum 50 characters. If omitted, it will be automatically generated f… |
No output schema declared.
No examples provided.
create_team_in_organization Create Team in Organization ~111
Create a new team within an organization using SCIM Groups protocol. The team is initialized with an empty member set, and the display name is normalized to lowercase with spaces converted to dashes.
| Name | Type | Req | Description |
|---|---|---|---|
| displayName | string | yes | The display name for the team as shown in the UI. This will be normalized to a URL-friendly slug format (lowercase, spaces converted to dashes). |
| 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.
delete_alert Delete Alert ~71
Permanently deletes an alert from a workflow. This endpoint is currently in beta and supported by New Monitors and Alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| workflow_id | integer | yes | The numeric ID of the alert to delete. |
No output schema declared.
No examples provided.
delete_alerts_bulk Delete Alerts in Bulk ~93
Bulk delete alerts for an organization, optionally filtered by a search query. This endpoint is currently in beta and supported by New Monitors and Alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| query | string | – | An optional search query to filter which alerts should be deleted. If omitted, the operation applies to all alerts in the organization. |
No output schema declared.
No examples provided.
delete_client_key Delete Client Key ~96
Permanently delete a client key from a project. This action cannot be undone and will invalidate the key for authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The unique identifier of the client key to be deleted. |
| 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.
delete_custom_integration Delete Custom Integration ~68
Permanently delete a custom integration (Sentry app) from your organization. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| sentry_app_id_or_slug | string | yes | The unique identifier or slug of the custom integration to delete. You can use either the numeric ID or the URL-friendly slug name. |
No output schema declared.
No examples provided.
delete_data_forwarder_for_organization Delete Data Forwarder for Organization ~74
Permanently deletes a data forwarder from an organization, including all associated project-specific overrides.
| Name | Type | Req | Description |
|---|---|---|---|
| data_forwarder_id | integer | yes | The numeric ID of the data forwarder to delete. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
delete_debug_information_file Delete Debug Information File ~118
Permanently delete a specific debug information file (DIF) from a project. This removes the debug symbols associated with the given DIF ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the debug information file to delete. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug of the organization that owns the project. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL-friendly slug of the project containing the debug information file to delete. |
No output schema declared.
No examples provided.
delete_discover_saved_query Delete Discover Saved Query ~69
Permanently delete a saved Discover query from an organization. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| query_id | integer | yes | The numeric ID of the saved Discover query to delete. |
No output schema declared.
No examples provided.
delete_external_issue Delete External Issue ~82
Delete an external issue linked to a Sentry app installation. This removes the association between the external issue and the integration platform.
| Name | Type | Req | Description |
|---|---|---|---|
| external_issue_id | string | yes | The unique identifier of the external issue to delete from the integration platform. |
| uuid | string | yes | The unique identifier of the Sentry app installation (integration platform integration) that owns the external issue. |
No output schema declared.
No examples provided.
delete_external_team_link Delete External Team Link ~138
Remove the integration link between an external team (from a provider like GitHub or Slack) and a Sentry team, effectively disconnecting the external team from Sentry's team management.
| Name | Type | Req | Description |
|---|---|---|---|
| external_team_id | integer | yes | The numeric ID of the external team link to delete, as returned when the external team integration was originally created. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization containing the team. |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL slug of the Sentry team to disconnect from the external provider. |
No output schema declared.
No examples provided.
delete_external_user Delete External User ~94
Remove the link between an external provider user and a Sentry user account, effectively disconnecting the external identity from the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| external_user_id | integer | yes | The unique identifier of the external user object to delete. This ID is provided when the external user is initially created. |
| 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.
delete_issue Delete Issue ~70
Permanently removes an individual issue from an organization. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | The unique identifier of the issue to be deleted. |
| 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.
delete_issue_alert_rule Delete Issue Alert Rule ~145
Delete a specific issue alert rule from a project. Issue alert rules trigger on new events matching specified conditions (such as resolved issues reappearing or issues affecting many users) and are configured with triggers, filters, and actions. Note: This endpoint is deprecated; use the Delete an Alert endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization that owns the project. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL slug of the project containing the alert rule. |
| rule_id | integer | yes | The numeric ID of the alert rule to delete. |
No output schema declared.
No examples provided.
delete_issues Delete Issues ~108
Permanently remove one or more issues from a project. Specify issue IDs via query parameters; the operation succeeds even if some IDs are invalid or out of scope without modifying any data.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either its numeric ID or URL slug. Used to scope the project and issues being deleted. |
| project_id_or_slug | string | yes | The project identifier, either its numeric ID or URL slug. Combined with the organization to locate the issues for deletion. |
No output schema declared.
No examples provided.
delete_monitor Delete Monitor ~90
Permanently delete a monitor (detector) from an organization. This beta endpoint is part of the New Monitors and Alerts system and may not yet be visible in the UI.
| Name | Type | Req | Description |
|---|---|---|---|
| detector_id | integer | yes | The numeric ID of the monitor to delete. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug of the organization that owns the monitor. |
No output schema declared.
No examples provided.
delete_monitor_for_project Delete Monitor for Project ~146
Delete a monitor or specific monitor environments within a project. Optionally target specific environments for deletion; if no environments are specified, the entire monitor is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Optional list of environment names to delete. When provided, only the specified environments are removed from the monitor; when omitted, the entire monitor is deleted. |
| monitor_id_or_slug | string | yes | The monitor identifier, either the numeric ID or the URL-friendly slug. |
| 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.
delete_monitor_or_monitor_environments Delete Monitor or Monitor Environments ~130
Delete a monitor or specific monitor environments. If environment names are provided, only those environments are deleted; otherwise, the entire monitor is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Optional list of environment names to delete. When specified, only these environments are removed from the monitor rather than deleting the entire monitor. Omit to delete the monitor entirely. |
| monitor_id_or_slug | string | yes | The monitor identifier, either the numeric ID or the URL slug of the monitor. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
No output schema declared.
No examples provided.
delete_monitors_bulk Delete Monitors in Bulk ~103
Bulk delete monitors for an organization, optionally filtered by search criteria. This beta endpoint supports the New Monitors and Alerts system.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 to delete. Supports filtering by name, type (error, metric_issue, issue_stream), or assignee (email, username, #team, me, none). |
No output schema declared.
No examples provided.
delete_organization_dashboard Delete Organization Dashboard ~69
Delete an organization's custom dashboard or tombstone a pre-built dashboard to effectively remove it from the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard_id | integer | yes | The numeric ID of the dashboard to delete. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
delete_organization_integration Delete Organization Integration ~87
Remove an integration from an organization. This operation requires both the Integration and OrganizationIntegration database entries to exist for the specified organization and integration.
| Name | Type | Req | Description |
|---|---|---|---|
| integration_id | string | yes | The unique identifier of the integration that is installed on the organization. |
| 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.
delete_organization_issues Delete Organization Issues ~156
Permanently remove issues from an organization. Specify issues by ID for precise deletion, or use query filters to target multiple issues. Returns success even if no matching issues are found.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Filter issues by one or more environment names. Only issues matching all specified environments will be affected. |
| limit | integer | – | Maximum number of issues to delete in this operation. Capped at 100 issues per request. |
| organization_id_or_slug | string | yes | The organization identifier, either its numeric ID or URL slug. |
| query | string | – | Search query to filter issues by status, assignee, or other criteria. Defaults to unresolved issues only. Use an empty string to match all issues regardless of status. |
No output schema declared.
No examples provided.
delete_organization_member Delete Organization Member ~75
Remove a member from an organization. This operation permanently deletes the member's association with the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The unique identifier of the organization member to remove. |
| 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.
delete_organization_release Delete Organization Release ~79
Permanently delete a release from an organization, including all associated files and artifacts. This action cannot be undone.
| 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. |
| version | string | yes | The version string that uniquely identifies the release within the organization. |
No output schema declared.
No examples provided.
delete_project Delete Project ~106
Schedules a project for deletion. The deletion process is asynchronous, so the project won't be immediately removed, but its state will change and it will be hidden from most public views once deletion begins.
| 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. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL slug of the project to be deleted. |
No output schema declared.
No examples provided.
delete_release_file Delete Release File ~95
Permanently delete a file associated with a specific release in an organization. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The unique identifier of the file to be deleted from the release. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL slug of the organization. |
| version | string | yes | The version string that uniquely identifies the release within the organization. |
No output schema declared.
No examples provided.
delete_release_file_for_project Delete Release File ~111
Permanently delete a file associated with a specific release. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The unique identifier of the file to be deleted from the release. |
| 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. |
| version | string | yes | The release version string used to identify the specific release. |
No output schema declared.
No examples provided.
delete_replay Delete Replay ~90
Permanently delete a replay instance from a project. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| replay_id | string | yes | The unique identifier (UUID) of the replay to delete. |
No output schema declared.
No examples provided.
delete_symbol_source Delete Symbol Source ~92
Remove a custom symbol source from a project. This permanently deletes the symbol source configuration and its associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the symbol source to delete. |
| 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.
delete_team Delete Team ~103
Schedules a team for deletion. The deletion process is asynchronous, so the team won't be immediately removed, but its slug will be released immediately while the deletion completes in the background.
| 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 to be deleted. |
No output schema declared.
No examples provided.
delete_team_from_project Delete Team from Project ~97
Revoke a team's access to a project. Team Admins can only revoke access for teams they administer.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL slug. |
No output schema declared.
No examples provided.
disable_spike_protection_for_projects Disable Spike Protection for Projects ~107
Disables Spike Protection for specified projects within an organization. Use the special value `$all` to disable Spike Protection across all projects in the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization containing the projects. |
| projects | array | yes | Array of project slugs to disable Spike Protection for. Use the special value `$all` to disable Spike Protection for all projects in the organization at once. |
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 PyPI package (mcparmory-sentry).
Is the com.mcparmory/sentry MCP server safe to use?
com.mcparmory/sentry scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.