Sentry Service Orchestrator (Node.js)

This utility acts as a Model Context Protocol (MCP) endpoint, facilitating communication with the Sentry Application Performance Monitoring (APM) platform. It empowers AI agents to pull detailed telemetry, triage reported failures, administer project settings, and analyze service responsiveness.

Prerequisites

Execution environment requires Node.js (version 14 or newer).
Dependency management via npm or yarn.
An active Sentry subscription with API access credentials.
A valid Sentry Personal API Token authorized for necessary scopes.

Initial Setup Procedures

Install required packages: bash npm install

IDE Integration Notes

This implementation has been confirmed compatible with Codeium Windsurf environments.

Note: Current integration status with Cursor's MCP framework indicates partial functionality; expect limitations.

Configuration for Claude Integration

To enable this endpoint for use with Claude, incorporate the following configuration structure into your Claude client settings:

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

Remember to substitute /Users/<your-user-directory>/mcp-sentry-ts/index.ts with the actual path in the args array.
Ensure <YOUR_AUTH_TOKEN> is replaced by your actual Sentry credential.

Available Operations (Tools)

list_projects

Fetches a roster of all Sentry projects visible within the specified organization.

Arguments: - organization_slug (Text, Mandatory): The unique identifier (slug) for the target organization. - view (Text, Optional): Defines data granularity: "summary" or "detailed" (Defaults to "detailed"). - format (Text, Optional): Output serialization type: "plain" or "markdown" (Defaults to "markdown").

resolve_short_id

Obtains comprehensive details pertaining to an error incident identified by its concise reference ID.

Arguments: - organization_slug (Text, Mandatory): The organization slug associated with the incident. - short_id (Text, Mandatory): The shorthand issue identifier (e.g., PROJECT-456). - format (Text, Optional): Output serialization type: "plain" or "markdown" (Defaults to "markdown").

get_sentry_event

Retrieves and performs preliminary analysis on a singular error telemetry event linked to an issue.

Arguments: - issue_id_or_url (Text, Mandatory): The Sentry issue identifier (numeric ID or full URL). - event_id (Text, Mandatory): The unique identifier for the specific event record. - view (Text, Optional): Defines data granularity: "summary" or "detailed" (Defaults to "detailed"). - format (Text, Optional): Output serialization type: "plain" or "markdown" (Defaults to "markdown").

list_error_events_in_project

Generates a log of error occurrences captured within a designated Sentry project.

Arguments: - organization_slug (Text, Mandatory): The slug of the organization hosting the project. - project_slug (Text, Mandatory): The project's unique slug identifier. - view (Text, Optional): Defines data granularity: "summary" or "detailed" (Defaults to "detailed"). - format (Text, Optional): Output serialization type: "plain" or "markdown" (Defaults to "markdown").

create_project

Provisions a novel project within Sentry and returns the resultant configuration keys for integration.

Arguments: - organization_slug (Text, Mandatory): The slug of the organization where creation should occur. - team_slug (Text, Mandatory): The slug identifying the team to which the new project belongs. - name (Text, Mandatory): The human-readable designation for the new project. - platform (Text, Optional): Specifies the technical environment/platform of the project. - view (Text, Optional): Defines data granularity: "summary" or "detailed" (Defaults to "detailed"). - format (Text, Optional): Output serialization type: "plain" or "markdown" (Defaults to "markdown").

list_project_issues

Retrieves a listing of reported issues affecting a specified Sentry project.

list_issue_events

Enumerates all recorded events associated with a particular Sentry incident.

Arguments: - organization_slug (Text, Mandatory): The slug of the organization containing the issue. - issue_id (Text, Mandatory): The primary identifier of the incident. - view (Text, Optional): Defines data granularity: "summary" or "detailed" (Defaults to "detailed"). - format (Text, Optional): Output serialization type: "plain" or "markdown" (Defaults to "markdown").

get_sentry_issue

Fetches and processes the details for a specified Sentry incident record.

Arguments: - issue_id_or_url (Text, Mandatory): The Sentry issue identifier (numeric ID or full URL). - view (Text, Optional): Defines data granularity: "summary" or "detailed" (Defaults to "detailed"). - format (Text, Optional): Output serialization type: "plain" or "markdown" (Defaults to "markdown").

list_organization_replays

Queries and returns a list of session replays recorded within the targeted Sentry organization.

Arguments: - organization_slug (Text, Mandatory): The slug identifying the organization being queried. - project_ids (List of Text, Optional): Filter replays by a list of associated project IDs. - environment (Text, Optional): Filter based on the deployment environment (e.g., 'staging'). - stats_period (Text, Optional): The timeframe window for statistics aggregation (e.g., "1h", "30d"). - start (Text, Optional): Timestamp marking the beginning of the retrieval period. - end (Text, Optional): Timestamp marking the conclusion of the retrieval period. - sort (Text, Optional): Criterion used to order the results. - query (Text, Optional): A free-text search predicate to refine the replay set. - per_page (Number, Optional): Maximum count of results returned per single API call. - cursor (Text, Optional): Token for navigating paginated results. - view (Text, Optional): Defines data granularity: "summary" or "detailed" (Defaults to "detailed"). - format (Text, Optional): Output serialization type: "plain" or "markdown" (Defaults to "markdown").

Server Execution

To initiate the process:

bash npx ts-node index.ts

Security Mandate

This service strictly necessitates a valid Sentry API authorization credential, obtainable via the Sentry account administration panel under 'API Keys'.

Failure Management

The server incorporates robust mechanisms for exception handling, specifically targeting: - Unavailability of the required access token. - Failures originating from external API calls. - Improper configuration of input parameters. - General network communication faults.

All encountered exceptions are directed to the standard console output for diagnostic review.

WIKIPEDIA CONTEXT SUPPLEMENT: Business orchestration solutions encompass the applications, methodologies, controls, and computational assets utilized by enterprises to navigate volatile market dynamics, maintain competitive advantage, and elevate operational efficacy. These systems span functional silos—from initial data capture and process governance to consolidated reporting and strategic forecasting. The efficacy of modern business tooling hinges not just on selection, but crucially on tailored implementation aligned with organizational imperatives.