Server Details
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
13 toolsanalyze_issue_with_seerInspect
Use Seer to analyze production errors and get detailed root cause analysis with specific code fixes.
Use this tool when:
The user explicitly asks for root cause analysis, Seer analysis, or help fixing/debugging an issue
You are unable to accurately determine the root cause from the issue details alone
Do NOT call this tool as an automatic follow-up to get_issue_details.
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
analyze_issue_with_seer(issueUrl='https://my-org.sentry.io/issues/PROJECT-1Z43')User: "Analyze this issue and suggest a fix"
analyze_issue_with_seer(organizationSlug='my-organization', issueId='ERROR-456')| Name | Required | Description | Default |
|---|---|---|---|
| issueId | No | The Issue ID. e.g. `PROJECT-1Z43` | |
| issueUrl | No | The URL of the issue. e.g. https://my-organization.sentry.io/issues/PROJECT-1Z43 | |
| regionUrl | No | 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. | |
| instruction | No | Optional custom instruction for the AI analysis | |
| organizationSlug | No | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. |
find_organizationsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search query to filter results by name or slug. Use this to narrow down results when there are many items. |
find_projectsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search query to filter results by name or slug. Use this to narrow down results when there are many items. | |
| regionUrl | No | 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. | |
| organizationSlug | Yes | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. |
find_releasesInspect
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_releases(organizationSlug='my-organization')Find releases matching '2ce6a27' in the 'my-organization' organization
find_releases(organizationSlug='my-organization', query='2ce6a27')| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search for versions which contain the provided string. | |
| regionUrl | No | 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 | No | The project's slug. This will default to all projects you have access to. It is encouraged to specify this when possible. | |
| organizationSlug | Yes | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. |
find_teamsInspect
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 and numeric ID 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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search query to filter results by name or slug. Use this to narrow down results when there are many items. | |
| regionUrl | No | 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. | |
| organizationSlug | Yes | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. |
get_event_attachmentInspect
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
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')| Name | Required | Description | Default |
|---|---|---|---|
| eventId | Yes | The ID of the event. | |
| regionUrl | No | 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 | Yes | The project's slug. You can find a list of existing projects in an organization using the `find_projects()` tool. | |
| attachmentId | No | The ID of the attachment to download. | |
| organizationSlug | Yes | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. |
get_issue_detailsInspect
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)
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 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')| Name | Required | Description | Default |
|---|---|---|---|
| eventId | No | The ID of the event. | |
| issueId | No | The Issue ID. e.g. `PROJECT-1Z43` | |
| issueUrl | No | The URL of the issue. e.g. https://my-organization.sentry.io/issues/PROJECT-1Z43 | |
| regionUrl | No | 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. | |
| organizationSlug | No | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. |
get_issue_tag_valuesInspect
Get tag value distribution for a specific Sentry issue.
Use this tool when you need to:
Understand how an issue is distributed across different tag values
Get aggregate counts of unique tag values (e.g., 'how many unique URLs are affected')
Analyze which browsers, environments, or URLs are most impacted by an issue
View the tag distributions page data programmatically
Common tag keys:
url: Request URLs affected by the issuebrowser: Browser types and versionsbrowser.name: Browser names onlyos: Operating systemsenvironment: Deployment environments (production, staging, etc.)release: Software releasesdevice: Device typesuser: Affected users
Get browser distribution using issue URL
get_issue_tag_values(issueUrl='https://sentry.io/issues/PROJECT-123/', tagKey='browser')Get environment distribution
get_issue_tag_values(organizationSlug='my-organization', issueId='PROJECT-123', tagKey='environment')| Name | Required | Description | Default |
|---|---|---|---|
| tagKey | Yes | The tag key to get values for (e.g., 'url', 'browser', 'environment', 'release'). | |
| issueId | No | The Issue ID. e.g. `PROJECT-1Z43` | |
| issueUrl | No | The URL of the issue. e.g. https://my-organization.sentry.io/issues/PROJECT-1Z43 | |
| regionUrl | No | 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. | |
| organizationSlug | No | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. |
get_trace_detailsInspect
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
| Name | Required | Description | Default |
|---|---|---|---|
| traceId | Yes | The trace ID. e.g. `a4d1aae7216b47ff8117cf4e09ce9d0a` | |
| regionUrl | No | 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. | |
| organizationSlug | Yes | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. |
search_eventsInspect
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
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| regionUrl | No | 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 | No | The project's slug. You can find a list of existing projects in an organization using the `find_projects()` tool. | |
| organizationSlug | Yes | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. | |
| includeExplanation | No | Include explanation of how the query was translated | |
| naturalLanguageQuery | Yes | Natural language description of what you want to search for |
search_issue_eventsInspect
Search and filter events within a specific issue using natural language queries.
Use this to filter events by time, environment, release, user, trace ID, or other tags. The tool automatically constrains results to the specified issue.
For cross-issue searches use search_issues, for single event details use get_issue_details.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of events to return (1-100, default: 50) | |
| issueId | No | Issue ID (e.g., 'MCP-41', 'PROJECT-123'). Requires organizationSlug. Alternatively, use issueUrl. | |
| issueUrl | No | Full Sentry issue URL (e.g., 'https://sentry.io/organizations/my-org/issues/123/'). Includes both organization and issue ID. | |
| regionUrl | No | Sentry region URL. Optional - defaults to main region. | |
| projectSlug | No | Project slug for better tag discovery. Optional - helps find project-specific tags. | |
| organizationSlug | No | Organization slug. Required when using issueId. Not needed when using issueUrl. | |
| includeExplanation | No | Include explanation of how the natural language query was translated to Sentry syntax | |
| naturalLanguageQuery | Yes | Natural language description of what events you want to find within this issue. Examples: 'from last hour', 'production with release v1.0', 'affecting user alice@example.com', 'with trace ID abc123' |
search_issuesInspect
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'
User feedback: 'show me user feedback', 'feedback from last week'
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!
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of issues to return | |
| regionUrl | No | 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. | |
| projectSlugOrId | No | The project's slug or numeric ID (optional) | |
| organizationSlug | Yes | The organization's slug. You can find a existing list of organizations you have access to using the `find_organizations()` tool. | |
| includeExplanation | No | Include explanation of how the query was translated | |
| naturalLanguageQuery | Yes | Natural language description of issues to search for |
whoamiInspect
Identify the authenticated user in Sentry.
Use this tool when you need to:
Get the user's name and email address.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!