Sentry
Sentry MCP Server
Retrieve the list of 11 available tools from Sentry. Tools: whoami, find_organizations, find_teams, find_projects, find_releases, get_issue_details, get_trace_details, get_event_attachment, search_events, analyze_issue_with_seer, search_issues
OAuth2 access token for authenticated requests
List of available tools
Unauthorized
Forbidden - User doesn't have access to this server
MCP server not found
Identify the authenticated user in Sentry.
Use this tool when you need to:
Get the user's name and email address.
Arguments:
OAuth2 access token for authenticated requests
Input parameters for whoami
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Find organizations that the user has access to in Sentry.
Use this tool when you need to:
View organizations in Sentry
Find an organization's slug to aid other tool requests
Search for specific organizations by name or slug
Returns up to 25 results. If you hit this limit, use the query parameter to narrow down results.
Arguments:
'query': Search query to filter results by name or slug. Use this to narrow down results when there are many items.
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Find teams in an organization in Sentry.
Use this tool when you need to:
View teams in a Sentry organization
Find a team's slug to aid other tool requests
Search for specific teams by name or slug
Returns up to 25 results. If you hit this limit, use the query parameter to narrow down results.
Arguments:
'organizationSlug' (required): The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
'query': Search query to filter results by name or slug. Use this to narrow down results when there are many items.
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Find projects in Sentry.
Use this tool when you need to:
View projects in a Sentry organization
Find a project's slug to aid other tool requests
Search for specific projects by name or slug
Returns up to 25 results. If you hit this limit, use the query parameter to narrow down results.
Arguments:
'organizationSlug' (required): The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
'query': Search query to filter results by name or slug. Use this to narrow down results when there are many items.
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Find releases in Sentry.
Use this tool when you need to:
Find recent releases in a Sentry organization
Find the most recent version released of a specific project
Determine when a release was deployed to an environment
### Find the most recent releases in the 'my-organization' organization
''' find_releases(organizationSlug='my-organization') '''
Find releases matching '2ce6a27' in the 'my-organization' organization
''' find_releases(organizationSlug='my-organization', query='2ce6a27') '''
- If the user passes a parameter in the form of name/otherName, its likely in the format of /.
Arguments:
'organizationSlug' (required): The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
'projectSlug': The project's slug. This will default to all projects you have access to. It is encouraged to specify this when possible.
'query': Search for versions which contain the provided string.
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Get detailed information about a specific Sentry issue by ID.
USE THIS TOOL WHEN USERS:
Provide a specific issue ID (e.g., 'CLOUDFLARE-MCP-41', 'PROJECT-123')
Ask to 'explain [ISSUE-ID]', 'tell me about [ISSUE-ID]'
Want details/stacktrace/analysis for a known issue
Provide a Sentry issue URL
DO NOT USE for:
General searching or listing issues (use search_issues)
Root cause analysis (use analyze_issue_with_seer)
TRIGGER PATTERNS:
'Explain ISSUE-123' → use get_issue_details
'Tell me about PROJECT-456' → use get_issue_details
'What happened in [issue URL]' → use get_issue_details
### With Sentry URL (recommended - simplest approach) ''' get_issue_details(issueUrl='https://sentry.sentry.io/issues/6916805731/?project=4509062593708032&query=is%3Aunresolved') '''
With issue ID and organization
''' get_issue_details(organizationSlug='my-organization', issueId='CLOUDFLARE-MCP-41') '''
With event ID and organization
''' get_issue_details(organizationSlug='my-organization', eventId='c49541c747cb4d8aa3efb70ca5aba243') '''
- **IMPORTANT**: If user provides a Sentry URL, pass the ENTIRE URL to issueUrl parameter unchanged - When using issueUrl, all other parameters are automatically extracted - don't provide them separately - If using issueId (not URL), then organizationSlug is required
Arguments:
'organizationSlug': The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
'issueId': The Issue ID. e.g. 'PROJECT-1Z43'
'eventId': The ID of the event.
'issueUrl': The URL of the issue. e.g. https://my-organization.sentry.io/issues/PROJECT-1Z43
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Get detailed information about a specific Sentry trace by ID.
USE THIS TOOL WHEN USERS:
Provide a specific trace ID (e.g., 'a4d1aae7216b47ff8117cf4e09ce9d0a')
Ask to 'show me trace [TRACE-ID]', 'explain trace [TRACE-ID]'
Want high-level overview and link to view trace details in Sentry
Need trace statistics and span breakdown
DO NOT USE for:
General searching for traces (use search_events with trace queries)
Individual span details (this shows trace overview)
TRIGGER PATTERNS:
'Show me trace abc123' → use get_trace_details
'Explain trace a4d1aae7216b47ff8117cf4e09ce9d0a' → use get_trace_details
'What is trace [trace-id]' → use get_trace_details
### Get trace overview ''' get_trace_details(organizationSlug='my-organization', traceId='a4d1aae7216b47ff8117cf4e09ce9d0a') ''' - Trace IDs are 32-character hexadecimal strings
Arguments:
'organizationSlug' (required): The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
'traceId' (required): The trace ID. e.g. 'a4d1aae7216b47ff8117cf4e09ce9d0a'
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Download attachments from a Sentry event.
Use this tool when you need to:
Download files attached to a specific event
Access screenshots, log files, or other attachments uploaded with an error report
Retrieve attachment metadata and download URLs
### Download a specific attachment by ID
''' get_event_attachment(organizationSlug='my-organization', projectSlug='my-project', eventId='c49541c747cb4d8aa3efb70ca5aba243', attachmentId='12345') '''
List all attachments for an event
''' get_event_attachment(organizationSlug='my-organization', projectSlug='my-project', eventId='c49541c747cb4d8aa3efb70ca5aba243') '''
- If 'attachmentId' is provided, the specific attachment will be downloaded as an embedded resource - If 'attachmentId' is omitted, all attachments for the event will be listed with download information - The 'projectSlug' is required to identify which project the event belongs to
Arguments:
'organizationSlug' (required): The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'projectSlug' (required): The project's slug. You can find a list of existing projects in an organization using the 'find_projects()' tool.
'eventId' (required): The ID of the event.
'attachmentId': The ID of the attachment to download.
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Search for events AND perform counts/aggregations - the ONLY tool for statistics and counts.
Supports TWO query types:
AGGREGATIONS (counts, sums, averages): 'how many errors', 'count of issues', 'total tokens'
Individual events with timestamps: 'show me error logs from last hour'
USE THIS FOR ALL COUNTS/STATISTICS:
'how many errors today' → returns count
'count of database failures' → returns count
'total number of issues' → returns count
'average response time' → returns avg()
'sum of tokens used' → returns sum()
ALSO USE FOR INDIVIDUAL EVENTS:
'error logs from last hour' → returns event list
'database errors with timestamps' → returns event list
'trace spans for slow API calls' → returns span list
Dataset Selection (AI automatically chooses):
errors: Exception/crash events
logs: Log entries
spans: Performance data, AI/LLM calls, token usage
DO NOT USE for grouped issue lists → use search_issues
search_events(organizationSlug='my-org', naturalLanguageQuery='how many errors today') search_events(organizationSlug='my-org', naturalLanguageQuery='count of database failures this week') search_events(organizationSlug='my-org', naturalLanguageQuery='total tokens used by model') search_events(organizationSlug='my-org', naturalLanguageQuery='error logs from the last hour') - If the user passes a parameter in the form of name/otherName, it's likely in the format of /. - Parse org/project notation directly without calling find_organizations or find_projects.
Arguments:
'organizationSlug' (required): The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'naturalLanguageQuery' (required): Natural language description of what you want to search for
'projectSlug': The project's slug. You can find a list of existing projects in an organization using the 'find_projects()' tool.
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
'limit': Maximum number of results to return
'includeExplanation': Include explanation of how the query was translated
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Use Seer to analyze production errors and get detailed root cause analysis with specific code fixes.
Use this tool when you need:
Detailed AI-powered root cause analysis
Specific code fixes and implementation guidance
Step-by-step troubleshooting for complex issues
Understanding why an error is happening in production
What this tool provides:
Root cause analysis with code-level explanations
Specific file locations and line numbers where errors occur
Concrete code fixes you can apply
Step-by-step implementation guidance
This tool automatically:
Checks if analysis already exists (instant results)
Starts new AI analysis if needed (~2-5 minutes)
Returns complete fix recommendations
### User: "What's causing this error? https://my-org.sentry.io/issues/PROJECT-1Z43"
''' analyze_issue_with_seer(issueUrl='https://my-org.sentry.io/issues/PROJECT-1Z43') '''
User: "Can you help me understand why this is failing in production?"
''' analyze_issue_with_seer(organizationSlug='my-organization', issueId='ERROR-456') '''
- Use this tool when you need deeper analysis beyond basic issue details - If the user provides an issueUrl, extract it and use that parameter alone - The analysis includes actual code snippets and fixes, not just error descriptions - Results are cached - subsequent calls return instantly
Arguments:
'organizationSlug': The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
'issueId': The Issue ID. e.g. 'PROJECT-1Z43'
'issueUrl': The URL of the issue. e.g. https://my-organization.sentry.io/issues/PROJECT-1Z43
'instruction': Optional custom instruction for the AI analysis
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Search for grouped issues/problems in Sentry - returns a LIST of issues, NOT counts or aggregations.
Uses AI to translate natural language queries into Sentry issue search syntax. Returns grouped issues with metadata like title, status, and user count.
USE THIS TOOL WHEN USERS WANT:
A LIST of issues: 'show me issues', 'what problems do we have'
Filtered issue lists: 'unresolved issues', 'critical bugs'
Issues by impact: 'errors affecting more than 100 users'
Issues by assignment: 'issues assigned to me'
DO NOT USE FOR COUNTS/AGGREGATIONS:
'how many errors' → use search_events
'count of issues' → use search_events
'total number of errors today' → use search_events
'sum/average/statistics' → use search_events
ALSO DO NOT USE FOR:
Individual error events with timestamps → use search_events
Details about a specific issue ID → use get_issue_details
REMEMBER: This tool returns a LIST of issues, not counts or statistics!
search_issues(organizationSlug='my-org', naturalLanguageQuery='critical bugs from last week') search_issues(organizationSlug='my-org', naturalLanguageQuery='unhandled errors affecting 100+ users') search_issues(organizationSlug='my-org', naturalLanguageQuery='issues assigned to me') - If the user passes a parameter in the form of name/otherName, it's likely in the format of /. - Parse org/project notation directly without calling find_organizations or find_projects. - The projectSlugOrId parameter accepts both project slugs (e.g., 'my-project') and numeric IDs (e.g., '123456').
Arguments:
'organizationSlug' (required): The organization's slug. You can find a existing list of organizations you have access to using the 'find_organizations()' tool.
'naturalLanguageQuery' (required): Natural language description of issues to search for
'projectSlugOrId': The project's slug or numeric ID (optional)
'regionUrl': The region URL for the organization you're querying, if known. For Sentry's Cloud Service (sentry.io), this is typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from the organization details using the 'find_organizations()' tool.
'limit': Maximum number of issues to return
'includeExplanation': Include explanation of how the query was translated
OAuth2 access token for authenticated requests
Tool execution result
Bad Request - Invalid tool arguments
Unauthorized
Forbidden - User doesn't have access to this server
MCP server or tool not found
Last updated