Critical Advisory

This implementation has been largely superseded by the more capable Sentry Remote-MCP Server, which offers expanded functionality (like authentication handling) and superior tooling. This standalone MCP server remains primarily for educational reference; production deployments should strongly favor the remote solution. Live demonstration available at https://mcp.sentry.dev

Sentry Model Context Protocol (MCP) Interface

This component furnishes an MCP server designed specifically for interacting with the Sentry service infrastructure. It furnishes capabilities enabling AI agents to query and interpret incident reports, administer development projects, and supervise application runtime metrics.

Prerequisites

Execution environment: Node.js (version 14 or newer)
Package management: npm or yarn
Sentry Access: An active Sentry account provisioned with necessary API credentials.
Authentication Material: A Sentry authorization token possessing requisite scope permissions.

Installation Procedure

Acquire dependencies: bash npm install

Integration with Development Environments

This MCP service has been successfully validated for operation within IDEs such as Cursor, Codeium Windsurf, and Claude Desktop.

Configuration for Claude Integration

To activate this gateway within your Claude settings, incorporate the following configuration structure:

{ "mcpServers": { "sentry": { "command": "npx", "args": ["ts-node", "/Users//sentry-mcp-ts/index.ts"], "env": { "SENTRY_AUTH": "" } } } }

Adjust the file path within the args section to match your local structure.
Substitute <YOUR_AUTH_TOKEN> with your actual Sentry credential.

Available Operations (Tools)

list_projects

Enumerates all Sentry projects accessible within a specified organization.

**Arguments (Parameters): ** - organization_slug (string, Mandatory): The unique organizational identifier (slug). - view (string, Optional): Desired information granularity, 'summary' or 'detailed' (Default: 'detailed'). - format (string, Optional): Output serialization style, 'plain' or 'markdown' (Default: 'markdown').

resolve_short_id

Fetches comprehensive data concerning an incident identified by its abbreviated index.

**Arguments (Parameters): ** - organization_slug (string, Mandatory): The organization slug where the incident resides. - short_id (string, Mandatory): The compact issue identifier (e.g., PROJECT-123). - format (string, Optional): Output serialization style, 'plain' or 'markdown' (Default: 'markdown').

get_sentry_event

Retrieves and analyzes the specifics of a singular Sentry event tied to an issue.

**Arguments (Parameters): ** - issue_id_or_url (string, Mandatory): Either the numeric issue identifier or the complete Sentry URL. - event_id (string, Mandatory): The precise identifier for the event in question. - view (string, Optional): Information depth setting, 'summary' or 'detailed' (Default: 'detailed'). - format (string, Optional): Output serialization style, 'plain' or 'markdown' (Default: 'markdown').

list_error_events_in_project

Generates a listing of error occurrences registered against a particular Sentry project.

**Arguments (Parameters): ** - organization_slug (string, Mandatory): The organization slug housing the project. - project_slug (string, Mandatory): The designated project slug. - view (string, Optional): Information depth setting, 'summary' or 'detailed' (Default: 'detailed'). - format (string, Optional): Output serialization style, 'plain' or 'markdown' (Default: 'markdown').

create_project

Provisions a novel project within Sentry and returns its associated client credential keys.

**Arguments (Parameters): ** - organization_slug (string, Mandatory): The organization where the new project will be instantiated. - team_slug (string, Mandatory): The team to which ownership of the project will be assigned. - name (string, Mandatory): The designated nomenclature for the forthcoming project. - platform (string, Optional): The intended technological stack/platform for the project. - view (string, Optional): Information depth setting, 'summary' or 'detailed' (Default: 'detailed'). - format (string, Optional): Output serialization style, 'plain' or 'markdown' (Default: 'markdown').

list_project_issues

Retrieves a catalog of outstanding issues associated with a designated Sentry project.

list_issue_events

Retrieves all recorded events pertaining to a specific Sentry incident record.

**Arguments (Parameters): ** - organization_slug (string, Mandatory): The organization slug where the incident resides. - issue_id (string, Mandatory): The definitive identifier for the incident. - view (string, Optional): Information depth setting, 'summary' or 'detailed' (Default: 'detailed'). - format (string, Optional): Output serialization style, 'plain' or 'markdown' (Default: 'markdown').

get_sentry_issue

Fetches and contextualizes the details of a specified Sentry issue.

**Arguments (Parameters): ** - issue_id_or_url (string, Mandatory): The numeric ID or the complete Web address of the issue. - view (string, Optional): Information depth setting, 'summary' or 'detailed' (Default: 'detailed'). - format (string, Optional): Output serialization style, 'plain' or 'markdown' (Default: 'markdown').

list_organization_replays

Retrieves session replays recorded within a designated Sentry organization boundary.

**Arguments (Parameters): ** - organization_slug (string, Mandatory): The slug identifying the organization for replay retrieval. - project_ids (string[], Optional): A list of project identifiers to confine the search scope. - environment (string, Optional): The operational setting (e.g., 'production') for filtering. - stats_period (string, Optional): The temporal duration for statistical aggregation (e.g., "7d"). - start (string, Optional): The commencement timestamp for the replay range. - end (string, Optional): The termination timestamp for the replay range. - sort (string, Optional): The data field dictating the sorting order. - query (string, Optional): Arbitrary search predicate to refine the replay set. - per_page (number, Optional): Maximum number of results to return per request. - cursor (string, Optional): Token for navigating paginated results. - view (string, Optional): Information depth setting, 'summary' or 'detailed' (Default: 'detailed'). - format (string, Optional): Output serialization style, 'plain' or 'markdown' (Default: 'markdown').

Server Execution

To initiate the gateway service:

npx ts-node index.ts

Security Credentials

This utility mandates the provision of a valid Sentry authorization token, ensuring it possesses the requisite permissions to interact with the Sentry API endpoints. These tokens are generated within the Sentry interface under Settings -> User Settings -> Auth Tokens.