sentry-investigator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_PROJECT | No | (Optional) Your default project slug | |
| SENTRY_AUTH_TOKEN | Yes | Your Sentry API token | |
| SENTRY_ORGANIZATION | Yes | Your Sentry organization slug |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sentry_issuesC | Fetch recent issues from Sentry for investigation |
| investigate_issueC | Investigate a specific Sentry issue by analyzing the codebase and providing explanations and fixes |
| analyze_stack_traceB | Analyze a stack trace and find related code in the codebase |
| get_jira_boardsA | Get list of available Jira boards for ticket creation |
| create_jira_ticketA | Create a Jira ticket from a Sentry issue and link them together |
| get_issue_typesB | Get available issue types for a Jira project |
| create_jira_from_sentryB | Create a Jira ticket directly from a Sentry issue with automatic linking and rich context |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vibe-Code-Agent/sentry-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server