Sentry Issues FAQs

Question 1

How do I integrate Sentry Issues with an LLM?

Accepted Answer

This tool provides structured output that LLMs can easily parse. You can use the output to analyze error patterns, identify root causes, and even suggest solutions. Refer to the cases in the readme for prompt examples.

Question 2

What are the input parameters for retrieving Sentry events?

Accepted Answer

For `get_single_event`, you'll need the Sentry event URL or ID, and optionally the organization and project IDs or slugs. For `get_project_events`, you'll need the project ID or slug, and optionally the organization ID or slug. The mode (tiny or huge) is also an optional parameter.

Question 3

What kind of information can I retrieve with this tool?

Accepted Answer

You can retrieve single Sentry event details by URL or ID using `get_single_event`. You can also fetch lists of events for a specific Sentry project using `get_project_events`. You can choose between 'tiny' and 'huge' modes to control the amount of detail returned.

Question 4

What are the environment variables required to run this tool?

Accepted Answer

You need to set the `SENTRY_HOST`, `SENTRY_ORG`, `SENTRY_PROJ`, and `SENTRY_USER_TOKEN` environment variables with your Sentry host, organization, project, and user token respectively.

Question 5

What is Sentry Issues MCP?

Accepted Answer

Sentry Issues MCP is a tool designed to retrieve Sentry issue details or lists of issues, making it easy to integrate with LLMs for automated analysis and debugging workflows. Note: As of version 1.0.5, 'getting issues' is deprecated, favoring the event API due to its similar response structure.

Sentry Issues

Sentry Issues

Key Features

Use Cases

Key Features

Use Cases