Sentry Model Interaction Agent (MIA)

This agent adheres to the Model Context Protocol (MCP) for seamless integration with Sentry's data services. It furnishes AI entities with functionalities to query and scrutinize exception logs, administer project settings, and oversee application health indicators via the Sentry REST interface.

Prerequisites

• Node.js environment (version 14 or newer is mandated)
• Package manager: npm or yarn
• An active Sentry subscription capable of API interaction
• A valid Sentry authentication credential possessing requisite access scopes

Deployment Instructions

1. Execute dependency installation: npm install

Integrated Development Environment (IDE) Usage Notes

This MCP implementation has been validated for compatibility with Codeium Windsurf environments.

Note: Current operational status with Cursor's MCP subsystem is incomplete; full functionality is pending.

Configuration for Claude Integration

To enable this service within the Claude framework, inject the following structure into your Claude configuration profile:

{
    "mcpServers": {
        "sentry": {
            "command": "npx",
            "args": ["ts-node", "/Users/<your-user-directory>/mcp-sentry-ts/index.ts"],
            "env": {
                "SENTRY_AUTH": "<YOUR_AUTH_TOKEN>"
            }
        }
    }
}

• Ensure the path specified in args reflects your local installation directory.
• Substitute <YOUR_AUTH_TOKEN> with your unique Sentry API key.

Available Operations (Tools)

list_projects

Retrieves a catalog of all viewable Sentry projects associated with a specified organization.

**Arguments (Parameters): ** - organization_slug (string, mandatory): The unique identifier (slug) of the target organization. - view (string, elective): Desired data presentation style: "summary" or "detailed" (defaults to "detailed"). - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

resolve_short_id

Fetches comprehensive details for an error aggregate identified by its compact ID.

**Arguments (Parameters): ** - organization_slug (string, mandatory): The organization slug housing the specific issue. - short_id (string, mandatory): The condensed issue reference, typically in the format PROJECT-XXX. - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

get_sentry_event

Downloads and processes data pertaining to a singular recorded telemetry event within an issue context.

**Arguments (Parameters): ** - issue_id_or_url (string, mandatory): The numeric Sentry ID or the complete URL pointing to the issue. - event_id (string, mandatory): The specific identifier for the event record being targeted. - view (string, elective): Desired data presentation style: "summary" or "detailed" (defaults to "detailed"). - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

list_error_events_in_project

Generates a compilation of error telemetry occurrences tied to a designated project within an organization.

**Arguments (Parameters): ** - organization_slug (string, mandatory): The organizational slug containing the project. - project_slug (string, mandatory): The project identifier from which to extract events. - view (string, elective): Desired data presentation style: "summary" or "detailed" (defaults to "detailed"). - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

create_project

Provisions a brand new project entity within Sentry and returns associated client initialization keys.

**Arguments (Parameters): ** - organization_slug (string, mandatory): The slug of the organization designated as the parent. - team_slug (string, mandatory): The slug identifier for the team receiving project ownership. - name (string, mandatory): The chosen descriptive moniker for the forthcoming project. - platform (string, elective): Specification of the operational environment/platform for the project. - view (string, elective): Desired data presentation style: "summary" or "detailed" (defaults to "detailed"). - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

list_project_issues

Enumerates all known issues affecting a specific Sentry project.

**Arguments (Parameters): ** - organization_slug (string, mandatory): The organizational slug housing the project. - project_slug (string, mandatory): The project identifier whose issues are being requested. - view (string, elective): Desired data presentation style: "summary" or "detailed" (defaults to "detailed"). - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

list_issue_events

Provides a chronological listing of all recorded occurrences (events) linked to a particular Sentry issue record.

**Arguments (Parameters): ** - organization_slug (string, mandatory): The slug of the organization where the issue resides. - issue_id (string, mandatory): The unique identifier of the parent issue. - view (string, elective): Desired data presentation style: "summary" or "detailed" (defaults to "detailed"). - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

get_sentry_issue

Fetches and interprets the diagnostic information associated with a specific Sentry issue aggregate.

**Arguments (Parameters): ** - issue_id_or_url (string, mandatory): The numeric identifier or the full web address pointing to the issue. - view (string, elective): Desired data presentation style: "summary" or "detailed" (defaults to "detailed"). - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

list_organization_replays

Retrieves a manifest of session replays recorded for a specified Sentry organization.

**Arguments (Parameters): ** - organization_slug (string, mandatory): The slug identifying the organizational entity. - project_ids (string[], elective): A collection of project identifiers used to narrow the replay set. - environment (string, elective): A filter parameter based on the deployment environment. - stats_period (string, elective): The timeframe window for included statistics (e.g., "24h", "7d"). - start (string, elective): Timestamp marking the beginning of the desired retrieval interval. - end (string, elective): Timestamp marking the conclusion of the desired retrieval interval. - sort (string, elective): The field criteria upon which the results should be ordered. - query (string, elective): Textual search predicate to refine the replay list. - per_page (number, elective): Limit on the count of replay records returned in one transaction. - cursor (string, elective): Token required for fetching subsequent pages of results. - view (string, elective): Desired data presentation style: "summary" or "detailed" (defaults to "detailed"). - format (string, elective): Output encoding preference: "plain" or "markdown" (defaults to "markdown").

Initiating the Service Endpoint

npx ts-node index.ts

Authorization Mechanism

Operation of this utility necessitates possession of a properly scoped Sentry authorization token. These keys can be generated within your personal Sentry configuration area under the 'API Keys' section.

Exception Management Protocols

The server incorporates robust safeguards for handling common failures, including: - Absence of the requisite authorization credential - Failures during API communication - Submission of malformed input parameters - Disruptions in the network fabric

All encountered errors are systematically logged to the standard output stream to facilitate diagnostics.

WIKIPEDIA: Cloud delivery systems describe an architectural model where computing resources—such as processing power, data storage, and network services—are provisioned as an elastic utility over the internet, as defined by the ISO standard. This concept is broadly termed "the cloud."

== Core Attributes == In 2011, the U.S. National Institute of Standards and Technology (NIST) codified five defining attributes essential to cloud environments. The precise NIST definitions are cataloged below:

Self-Service Provisioning: "A consumer possesses the autonomy to unilaterally provision computational capacities, including server uptime and distributed repository space, as required, through automated means, bypassing the necessity for direct personnel intervention with the service supplier." Ubiquitous Network Entry: "Service capabilities are accessible via a network, utilizing standardized access methods that encourage uptake across diverse client platforms, both thin and feature-rich (e.g., smartphones, slates, portable computers, and desktop stations)." Consolidated Resource Allocation: "The supplier's collective computational assets are aggregated to service numerous consumers under a multi-tenant paradigm, wherein distinct physical and virtual assets are dynamically allocated and reallocated contingent upon consumer demand fluctuations." Elastic Scalability: "Capacities possess the ability to be scaled up or down fluidly, sometimes autonomously, enabling rapid expansion or retraction in proportion to workload necessity. From the user's perspective, the available provisioning options often appear limitless and instantly appropriable in any volume." Usage Metering: "Cloud architectures automatically oversee and maximize resource utilization by employing measurement functions at an appropriate level of abstraction for the service type (e.g., data capacity, computational cycles, data transfer rates, and active user entitlements). Consumption metrics are trackable, manageable, and reportable, ensuring transparency for both the provider and the recipient of the consumed resource. By the year 2023, the International Organization for Standardization (ISO) had progressed in refining and extending this foundational list.

== Historical Context ==

The conceptual lineage of cloud computing traces back to the 1960s, with early popularization of time-sharing techniques facilitated by remote job entry (RJE) protocols. During this period, the prevailing operational paradigm involved a "data center" model where users submitted computational tasks to dedicated operators for execution on mainframe systems. This era was characterized by intensive investigation into methodologies for democratizing access to large-scale computational power for broader user bases through time-sharing concepts, optimizing the underlying infrastructure, platform layers, and application stacks, thereby boosting end-user effectiveness. The graphical representation of virtualization as a "cloud" entity originated in 1994, employed by General Magic to depict the conceptual expanse of 'locations' accessible to mobile software agents within their Telescript framework. This visual convention is attributed to David Hoffman, a communications strategist at General Magic, derived from its established usage within telecommunications and network schematics. The explicit phrase "cloud computing" gained broader recognition in 1996 when Compaq Computer Corporation developed a strategic business blueprint for the emerging Internet landscape. The organization's core aspiration centered on leveraging the Internet to achieve pervasive access to computing resources.