codex-sentry-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_ORG | Yes | Your Sentry organization slug | |
| SENTRY_PROJECT | Yes | Your Sentry project slug | |
| SENTRY_AUTH_TOKEN | Yes | Your Sentry authentication token |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_latest_sentry_errorsB | Fetch the latest unresolved error logs and issues from Sentry |
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 1 tool
Only one tool exists, so there is no risk of confusing it with other tools.
With a single tool, naming consistency is moot, but the name follows a clear verb_noun pattern and is descriptive.
A single tool is borderline for a server aimed at Sentry error monitoring; it feels thin but is focused on a specific task.
The server only retrieves errors, lacking common operations like resolving, acknowledging, or filtering errors, leaving significant gaps for typical Sentry workflows.