Important Notice Regarding Tool Evolution

This particular instantiation of the Sentry MCP server is primarily maintained for historical reference and didactic purposes, serving as a foundational, self-contained server model. The official Sentry ecosystem has largely transitioned to the more feature-rich and secure Sentry Remote-MCP Server. For modern deployments requiring advanced features like integrated authentication and superior developer tooling, utilization of the remote version is strongly advised. This standalone version can be observed operating live at https://mcp.sentry.dev.

Sentry Model Context Protocol Endpoint

This component bridges AI assistants with the Sentry service fabric via the MCP framework. It grants programmatic access to error reports, performance metrics, and organizational configuration endpoints within Sentry.

Prerequisites for Operation

• A functioning Node.js runtime environment (version 14 or newer).
• A package manager: npm or yarn.
• Active Sentry subscription credentials.
• A securely generated Sentry authentication token possessing the requisite API scopes.

Configuration Steps

1. Initialize project dependencies:

npm install

Integration with Development Environments

Compatibility testing confirms successful operation with IDEs such as Cursor, Codeium Windsurf, and Claude Desktop environments.

Integration with Claude Systems

To incorporate this endpoint into your Claude configuration settings, append the following JSON structure to your preferences file:

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

• Path Modification: Ensure /Users/<your-user-directory>/sentry-mcp-ts/index.ts accurately reflects the binary's location on your filesystem.
• Token Substitution: Replace <YOUR_AUTH_TOKEN> with your actual, authorized Sentry access key.

Available Functions (Tools)

list_projects

Retrieves a catalogue of all Sentry projects accessible within a specified organization.

**Arguments (Parameters):

• organization_slug (String, Mandatory): The unique identifier string for the organization.
• view (String, Optional): Defines the level of detail; options are "summary" or "detailed" (default: "detailed").
• format (String, Optional): Specifies the output serialization; options are "plain" or "markdown" (default: "markdown").

resolve_short_id

Fetches comprehensive data pertaining to an issue identified via its short-form ID.

**Arguments (Parameters):

• organization_slug (String, Mandatory): The organization identifier where the issue resides.
• short_id (String, Mandatory): The concise issue reference (e.g., PROJECT-123).
• format (String, Optional): Output structure preference: "plain" or "markdown" (default: "markdown").

get_sentry_event

Acquires and parses the telemetry for a singular event associated with an issue.

**Arguments (Parameters):

• issue_id_or_url (String, Mandatory): The numeric ID or the complete Sentry URL pointing to the issue.
• event_id (String, Mandatory): The unique identifier for the specific event record.
• view (String, Optional): Detail level setting: "summary" or "detailed" (default: "detailed").
• format (String, Optional): Output representation: "plain" or "markdown" (default: "markdown").

list_error_events_in_project

Generates a list of all recorded error occurrences within a designated project.

**Arguments (Parameters):

• organization_slug (String, Mandatory): The organization slug.
• project_slug (String, Mandatory): The project slug whose events are to be listed.
• view (String, Optional): Presentation style: "summary" or "detailed" (default: "detailed").
• format (String, Optional): Result formatting: "plain" or "markdown" (default: "markdown").

create_project

Provisions a completely new project within the Sentry environment and returns its initial configuration keys.

**Arguments (Parameters):

• organization_slug (String, Mandatory): The target organization for project creation.
• team_slug (String, Mandatory): The team identifier to which the new project will be affiliated.
• name (String, Mandatory): The descriptive name for the forthcoming project.
• platform (String, Optional): The technological stack identifier for the project.
• view (String, Optional): Output detail level: "summary" or "detailed" (default: "detailed").
• format (String, Optional): Output schema: "plain" or "markdown" (default: "markdown").

list_project_issues

Retrieves all outstanding or resolved issues linked to a specific Sentry project.

**Arguments (Parameters):

• organization_slug (String, Mandatory): The controlling organization slug.
• project_slug (String, Mandatory): The project identifier to query issues from.
• view (String, Optional): Verbosity setting: "summary" or "detailed" (default: "detailed").
• format (String, Optional): Rendering choice: "plain" or "markdown" (default: "markdown").

list_issue_events

Enumerates all recorded events collected under a specific Sentry issue.

**Arguments (Parameters):

• organization_slug (String, Mandatory): The organization context.
• issue_id (String, Mandatory): The numerical identifier of the issue to inspect.
• view (String, Optional): Level of data presentation: "summary" or "detailed" (default: "detailed").
• format (String, Optional): Output rendering: "plain" or "markdown" (default: "markdown").

get_sentry_issue

Fetches and processes the full details for a given Sentry issue entity.

**Arguments (Parameters):

• issue_id_or_url (String, Mandatory): The issue's numerical ID or its complete web address.
• view (String, Optional): Detail granularity: "summary" or "detailed" (default: "detailed").
• format (String, Optional): Output format preference: "plain" or "markdown" (default: "markdown").

list_organization_replays

Queries and presents session replay records associated with an organization.

**Arguments (Parameters):

• organization_slug (String, Mandatory): The organization namespace.
• project_ids (String[], Optional): A list of project numeric identifiers for filtering.
• environment (String, Optional): Filters replays by their designated application environment tag.
• stats_period (String, Optional): Time window for statistics aggregation (e.g., "24h", "7d").
• start (String, Optional): Timestamp marking the beginning of the search period.
• end (String, Optional): Timestamp marking the conclusion of the search period.
• sort (String, Optional): Specifies the field by which the results should be ordered.
• query (String, Optional): A full-text search string to narrow down replay records.
• per_page (Number, Optional): Maximum number of results returned per API call.
• cursor (String, Optional): Token used for navigating to subsequent pages of results.
• view (String, Optional): Output complexity: "summary" or "detailed" (default: "detailed").
• format (String, Optional): Final presentation style: "plain" or "markdown" (default: "markdown").

Execution Command

To launch the server process locally:

npx ts-node index.ts

Authorization Protocol

Successful operation mandates providing a valid Sentry access token with permissions scoped to the intended API operations. These tokens are securely generated via the Sentry web interface under Settings -> User Settings -> Auth Tokens.