Bugsnag

Tool to view an organization by its ID. Use when you need to retrieve detailed information about a specific Bugsnag organization.

List all errors in a Bugsnag project with optional filtering and sorting. Use this to retrieve error summaries including error class, message, severity, status, occurrence counts, and affected users. Results are paginated; follow pagination indicators to retrieve all pages. No status filter parameter exists — filter by open/fixed/ignored status client-side using the status field in responses. Requires a valid project_id which can be obtained from the List Projects action.

Lists individual error event occurrences for a specific error group. Use this after identifying an error_id via BUGSNAG_LIST_ERRORS_ON_PROJECT to retrieve detailed stack traces, metadata, and context for each occurrence. Returns events sorted by timestamp (newest first by default). Supports pagination via 'base' parameter and filtering by event fields.

Tool to list teams in an organization. Use when you need to retrieve teams for a specified Bugsnag organization, optionally filtered by team name.

Tool to retrieve details of a specific configured integration by its ID. Returns configuration details, status, automation settings, and usage information. Use 'List Configured Integrations for Project' to obtain valid integration IDs.

Tool to view the project count of collaborators in an organization. Use when you need to retrieve project access counts for specific collaborators.

Tool to view projects a collaborator has access to in an organization. Use when you need to list all projects that a specific user can access within an organization.

Tool to check the status of an organization event data deletion request in Bugsnag. Use this to monitor deletion requests including their current status (PREPARING, AWAITING_CONFIRMATION, ACCEPTED, IN_PROGRESS, COMPLETED, EXPIRED), applied filters, and progress details.

Tool to check the status of an organization event data request. Use when you need to monitor the progress of a data export or GDPR request.

Tool to show the details of a team in an organization. Use when you need to retrieve information about a specific team including its name, collaborator count, and project count.

Tool to create a new project in a Bugsnag organization. Use when you need to set up a new project for error tracking under a specific organization. Requires organization_id, project name, and platform type. Optionally configure browser filtering for JavaScript projects.

Tool to add a collaborator to a group of teams in a Bugsnag organization. Use when you need to assign a collaborator to specific teams or all teams. Requires admin permissions on the organization.

Tool to add collaborators to a team in a Bugsnag organization. Use when you need to add specific collaborators or all organization collaborators to a team. Requires admin permissions on the organization.

Tool to configure a new integration for a Bugsnag project. Use after selecting integration key and preparing credentials.

Creates a custom event field for a Bugsnag project, enabling filtering and pivoting on custom metadata. Use this tool when you need to create a new searchable/filterable field from event metaData. Requires a project_id (get from BUGSNAG_LIST_PROJECTS), a unique display_id for the filter, and the path to the data in event metaData. Example: Create a custom field to filter by user account ID: - display_id: "custom.user.accountId" - path: "metaData.user.accountId" - filter_options: {"name": "Account ID", "match_types":

Tool to create an event data request for a Bugsnag organization (GDPR/CCPA compliance). Use when you need to export event data for a specific user or set of conditions to comply with data access requests. The request is processed asynchronously - check the status field and use the returned ID to monitor progress. Once completed, the url field provides a download link for the data export.

Tool to create a new team in a Bugsnag organization. Use when you need to organize collaborators into teams for better access management. The team name must be unique within the organization.

Tool to create an event data request for a Bugsnag project. Use when you need to export event data matching specific filters. The request is processed asynchronously - check the returned status and use the provided ID to poll for completion. Once completed, the 'url' field provides a download link for the event data. Supports GDPR/data subject access requests via the 'gdpr' report_type.

Creates a saved search (filterset) for a Bugsnag project that persists filter and sort configurations. Use this to save frequently used error filters for quick access in the dashboard. Requires a valid project_id which can be obtained from the list_projects action. The saved search can be made the project default and/or shared with collaborators.

Invites a new collaborator to a Bugsnag organization by email. Use this action to grant a user access to the organization. Optionally specify project_ids to restrict access to specific projects, or set admin=true to grant full admin privileges across all projects. Returns the collaborator details including their invitation status (pending_invitation=true until they accept). Re-inviting an existing email returns the existing collaborator data.

Tool to update a collaborator's project access permissions. Use when you need to change which projects a collaborator can access or their roles within each project. Supply only project_ids or project_roles.

Bulk update multiple errors in a Bugsnag project. Applies the same operation to all specified errors. Note: The actual API implementation returns only the operation name in the response, not per-error results. This differs from the OpenAPI specification which documents detailed per-error results. A successful response indicates the bulk operation was accepted and applied to all specified errors. Use cases: - Mark multiple errors as fixed after a release - Assign errors to a team member for investigation - Snooze or ignore low-priority errors in bulk - Link multiple related errors to a single issue tracker ticket - Change severity levels across related errors Prerequisites: Obtain project_id from BUGSNAG_LIST_PROJECTS and error_ids from BUGSNAG_LIST_ERRORS_ON_PROJECT.

Confirms a project event data deletion request in Bugsnag. Use this action after creating a deletion request to confirm and proceed with the actual deletion of event data. The deletion request must be in AWAITING_CONFIRMATION status before it can be confirmed.

Tool to create an event data deletion request for GDPR/CCPA compliance. Use when you need to delete event data matching specific criteria (e.g., user email, error class, device info). Specify filters to target events - most common is filtering by user.email. The deletion processes asynchronously; check the returned status and id to track progress. Requires organization administrator permissions.

Tool to create an event data deletion request for a specific project. Use when you need to delete event data matching specific criteria (e.g., error class, severity, user email) within a project. Specify filters to target events - most common is filtering by event.class or user.email. The deletion processes asynchronously; check the returned status and id to track progress.

Tool to delete a configured integration. Use when you need to remove an existing integration from a project after confirming the integration ID. This action cannot be undone and requires Organization Administrator or Project Owner permissions.

Permanently deletes all errors and event data from a Bugsnag project. WARNING: This action is IRREVERSIBLE. All error and event data will be permanently removed. Requirements: - User must have Project Owner or Organization Administrator permissions - A valid project_id is required (use BUGSNAG_LIST_PROJECTS to retrieve project IDs) Use this tool when you need to clear all error history from a project, such as during cleanup operations or before a major release.

Removes a collaborator from a Bugsnag organization. This action permanently revokes the user's access to all projects within the organization. Before using, obtain the organization_id from List Organizations and the collaborator_id from List Collaborators. Requires Organization Administrator privileges. Cannot remove the last admin of an organization.

Deletes a custom event field from a Bugsnag project. Use this tool when you need to remove a custom event field that was previously created via BUGSNAG_CREATE_CUSTOM_EVENT_FIELD. This action only works for custom event fields (where 'custom' is true) - built-in event fields cannot be deleted. Prerequisites: - Get the project_id from BUGSNAG_LIST_PROJECTS - Get the display_id from BUGSNAG_LIST_EVENT_FIELDS_FOR_PROJECT (filter for custom: true) Note: Requires a Bugsnag Preferred or Enterprise plan to use custom event fields.

Permanently deletes a Bugsnag organization. This action is irreversible and removes all organization data including projects, collaborators, and settings. Use BUGSNAG_LIST_ORGANIZATIONS to find the organization_id. Requires Organization Administrator permissions. Note: Heroku organizations cannot be deleted via the API.

Tool to delete a team from a Bugsnag organization. Use when you need to permanently remove a team. Requires organization admin permissions.