javaDer mcp sentry custom

WHAT IT CONNECTS

What javaDer mcp sentry custom gives an AI Agent

• **`get_sentry_issue`**
• **Description**: Retrieve and analyze a specific Sentry issue by its ID or URL.
• **Input**:
• `issue_id_or_url` (string): The Sentry issue ID or full URL to analyze.
• **Returns**: Detailed issue information, including:
• Title
• Issue ID
• Status
• Level
• First seen timestamp
• Last seen timestamp
• Event count
• Full stack trace
• **`get_list_issues`**
• **Description**: Retrieve and analyze a list of Sentry issues for a specific project.
• **Input**:
• `project_slug` (string): The Sentry project slug.
• `organization_slug` (string): The Sentry organization slug.
• **Returns**: A list of issues with details, including:
• Title
• Issue ID
• Status
• Level
• First seen timestamp
• Last seen timestamp
• Event count
• Basic issue information
• **`sentry-issue`**
• **Description**: Retrieve formatted issue details from Sentry for use in conversation context.
• **Input**:
• `issue_id_or_url` (string): The Sentry issue ID or URL.
• **Returns**: Formatted issue details.
• **Formatting**: Used proper Markdown headings, lists, and code blocks for readability.
• **Consistency**: Standardized terminology (e.g., `mcp_sentry` vs. `mcp-sentry-custom`) and removed redundant `<TEXT>` and `<JSON>` tags.
• **Clarity**: Rewrote sections like "Overview" and "Features" for conciseness and precision.
• **Completeness**: Fixed incomplete sentences and ensured all configuration examples were properly structured.
• **Professional Tone**: Adjusted wording to sound more formal and polished.