Sentry MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_URL | No | Base URL for Sentry, used for self-hosted instances | https://sentry.io |
| SENTRY_CLIENT_ID | No | Client ID for the Sentry OAuth application | |
| SENTRY_AUTH_TOKEN | Yes | Sentry authentication token with required scopes (org:read project:read project:write team:read team:write event:read) | |
| SENTRY_CLIENT_SECRET | No | Client secret for the Sentry OAuth application |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_organizationsB | List all organizations that the user has access to in Sentry. Use this tool when you need to:
|
| list_teamsA | List all teams in an organization in Sentry. Use this tool when you need to:
|
| list_projectsB | Retrieve a list of projects in Sentry. Use this tool when you need to:
|
| get_error_detailsA | Retrieve error details from Sentry for a specific Issue ID, including the stacktrace and error message. Either issueId or issueUrl MUST be provided. Use this tool when you need to:
|
| search_errors_in_fileA | Search for errors recently occurring in a specific file. This is a suffix based search, so only using the filename or the direct parent folder of the file. The parent folder is preferred when the filename is in a subfolder or a common filename. Use this tool when you need to:
|
| create_teamB | Create a new team in Sentry. Use this tool when you need to:
|
| create_projectB | Create a new project in Sentry, giving you access to a new SENTRY_DSN. Use this tool when you need to:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have distinct purposes, such as create_project vs. list_projects, but get_error_details and search_errors_in_file could potentially overlap in error investigation scenarios, which might cause slight confusion. Overall, the boundaries are clear with only minor ambiguity.
All tools follow a consistent verb_noun naming pattern using snake_case, such as create_project, list_organizations, and search_errors_in_file. This uniformity makes the tool set predictable and easy to understand.
With 7 tools, the count is reasonable for a Sentry-focused server, covering core operations like project, team, and error management. However, it feels slightly thin as it lacks update or delete operations, which are common in such domains.
The tool set covers creation and listing for projects, teams, and organizations, plus error retrieval and search, but it has notable gaps. Missing update/delete tools for projects and teams, and no error resolution or comment features, limit full lifecycle coverage for Sentry's domain.