Sentry Issues
About
Integrates with Sentry error tracking to retrieve detailed event and issue data for analyzing application exceptions and errors in development workflows.
Details
- Author
- leee62
- Repository
- Leee62/sentry-issues-mcp
- GitHub stars
- 3
- Downloads
- 306
- License
- MIT License
- Categories
- Productivity, Workplace, Developer Tools, AI, Communication, Infrastructure, Project Management, Security
Jump to
- EZ size
- EZ understand
- EZ tiny
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Sentry IssuesCommand (node, npx, python, etc.)npxArguments-
Argument 1
-y -
Argument 2
sentry-issues-mcp@latest
Environment-
SENTRY_ORG
<your_sentry_org> -
SENTRY_HOST
<your_sentry_host> -
SENTRY_PROJ
<your_sentry_proj> -
SENTRY_USER_TOKEN
<your_sentry_user_token>
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
-
Argument 1
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
this is MCP Server Config
"mcpServers": {
"sentry-issue-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sentry-issues-mcp@latest"
],
"env": {
"SENTRY_HOST": "<your_sentry_host>",
"SENTRY_ORG": "<your_sentry_org>",
"SENTRY_PROJ": "<your_sentry_proj>",
"SENTRY_USER_TOKEN": "<your_sentry_user_token>"
}
}
}
get_single_event
Get detailed information about a single event. Parameters: url_or_id (string), organization_id_or_slug (optional string), project_id_or_slug (optional string), mode (optional string - 'tiny' or 'huge')
get_project_events
Retrieve a list of events for a specific project. Parameters: project_id_or_slug (string), organization_id_or_slug (optional string), mode (optional string - 'tiny' or 'huge')
- get_single_event
- get a event detail infos, tiny mode return stack info, huge mode return all info
- inputs:
- url_or_id: sentry event url or sentry event id
- organization_id_or_slug: sentry organization id or slug, it can be undefined
- project_id_or_slug: sentry project id or slug, it can be undefined
- mode: tiny or huge, it can be undefined
- get_project_events
- get list of events, tiny mode return id and title, huge mode return all info
- inputs:
- project_id_or_slug: sentry project id or slug
- organization_id_or_slug: sentry organization id or slug, it can be undefined
- mode: tiny or huge, it can be undefined
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"sentry issues": {
"env": {
"SENTRY_ORG": "<your_sentry_org>",
"SENTRY_HOST": "<your_sentry_host>",
"SENTRY_PROJ": "<your_sentry_proj>",
"SENTRY_USER_TOKEN": "<your_sentry_user_token>"
},
"args": [
"-y",
"sentry-issues-mcp@latest"
],
"command": "npx"
}
}
}Linux
{
"env": {
"SENTRY_ORG": "<your_sentry_org>",
"SENTRY_HOST": "<your_sentry_host>",
"SENTRY_PROJ": "<your_sentry_proj>",
"SENTRY_USER_TOKEN": "<your_sentry_user_token>"
},
"args": [
"-y",
"sentry-issues-mcp@latest"
],
"command": "npx"
}Macos
{
"env": {
"SENTRY_ORG": "<your_sentry_org>",
"SENTRY_HOST": "<your_sentry_host>",
"SENTRY_PROJ": "<your_sentry_proj>",
"SENTRY_USER_TOKEN": "<your_sentry_user_token>"
},
"args": [
"-y",
"sentry-issues-mcp@latest"
],
"command": "npx"
}Windows
{
"env": {
"SENTRY_ORG": "<your_sentry_org>",
"SENTRY_HOST": "<your_sentry_host>",
"SENTRY_PROJ": "<your_sentry_proj>",
"SENTRY_USER_TOKEN": "<your_sentry_user_token>"
},
"args": [
"/c",
"npx",
"-y",
"sentry-issues-mcp@latest"
],
"command": "cmd"
}sentry-issue-mcp
Description
> ⚠️ Getting issues is deprecated as of version 1.0.5. The response structure is so similar to the event API that it's considered redundant.
This is a mcp for sentry issue.\
It supports 2 tools to get a issue or list of issues.\
U can let LLM analysis the Res, or u want to do.
Feature
- EZ size
- EZ understand
- EZ tiny
Tools
- get_single_event
- get a event detail infos, tiny mode return stack info, huge mode return all info
- inputs:
- url_or_id: sentry event url or sentry event id
- organization_id_or_slug: sentry organization id or slug, it can be undefined
- project_id_or_slug: sentry project id or slug, it can be undefined
- mode: tiny or huge, it can be undefined
- get_project_events
- get list of events, tiny mode return id and title, huge mode return all info
- inputs:
- project_id_or_slug: sentry project id or slug
- organization_id_or_slug: sentry organization id or slug, it can be undefined
- mode: tiny or huge, it can be undefined
QuickStart
this is MCP Server Config
"mcpServers": {
"sentry-issue-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sentry-issues-mcp@latest"
],
"env": {
"SENTRY_HOST": "<your_sentry_host>",
"SENTRY_ORG": "<your_sentry_org>",
"SENTRY_PROJ": "<your_sentry_proj>",
"SENTRY_USER_TOKEN": "<your_sentry_user_token>"
}
}
}
Case
- Ask LLM to analysis one issue by url or id
1. input "analysis the issue, and give me the reason of it, and tell me how to fix it, {sentry_issue_url}"
2. if ur LLM is SMART🧠, it will call tools
3. u will get result
- Ask LLM to find Today most dangerous issue (PS: default val of sentry time period is "24h")
1. input "find today most dangerous issue, and give me the reason of it, and tell me how to fix it"
2. if ur LLM is SMART🧠, it will call tools
3. u will get result
License
MIT
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
