F
licenseB
qualityD
maintenanceA Model Context Protocol server that retrieves and analyzes Sentry.io issues, allowing users to inspect error reports, stacktraces, and debugging information from their Sentry account.
2
22
-
Sentry
Server Details
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
get_profile_details7 fields changed- changed
Input schema / properties / end / descriptionPrevious value: -"End time for the profile chunk query (ISO 8601 format, e.g., '2024-01-01T01:00:00')"New value: +"Continuous profile end time in ISO 8601 format, for example '2024-01-01T01:00:00Z'" - changed
Input schema / properties / focusOnUserCode / descriptionPrevious value: -"Show only user code (in_app: true). Set to false to include library code."New value: +"Show only user code frames in the hotspot table. Set to false to include library frames." - added
Input schema / properties / profileIdAdded value: +{ + "description": "Transaction profile ID from a profile flamegraph URL", + "type": "string" +} - added
Input schema / properties / profileUrlAdded value: +{ + "description": "Sentry transaction profile or continuous profile URL. If provided, organization, project, and profile identifiers are extracted from the URL.", + "format": "uri", + "type": "string" +} - changed
Input schema / properties / profilerId / descriptionPrevious value: -"Profiler session ID (UUID from Sentry profile data)"New value: +"Continuous profiler session ID" - changed
Input schema / properties / start / descriptionPrevious value: -"Start time for the profile chunk query (ISO 8601 format, e.g., '2024-01-01T00:00:00')"New value: +"Continuous profile start time in ISO 8601 format, for example '2024-01-01T00:00:00Z'" - removed
Input schema / requiredRemoved value: -[ - "organizationSlug", - "projectSlugOrId", - "profilerId", - "start", - "end" -]
1 tool update
- Changed
get_replay_details1 field changed- changed
Input schema / properties / replayUrl / descriptionPrevious value: -"The URL of the replay. e.g. https://my-organization.sentry.io/replays/7e07485f-12f9-416b-8b14-26260799b51f/"New value: +"The URL of the replay. e.g. https://my-organization.sentry.io/explore/replays/7e07485f-12f9-416b-8b14-26260799b51f/"
1 tool update
- Changed
get_replay_details1 field changed- added
Input schema / properties / regionUrlAdded value: +{ + "anyOf": [ + { + "description": "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.", + "type": "string" + }, + { + "type": "null" + } + ], + "description": "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." +}
2 tool updates
- Added
get_replay_details - Changed
get_sentry_resource1 field changed- changed
Input schema / properties / resourceType / enumPrevious value: -[ - "issue", - "event", - "trace", - "breadcrumbs" -]New value: +[ + "issue", + "event", + "trace", + "breadcrumbs", + "replay" +]
1 tool update
- Added
get_profile_details
3 tool updates
- Removed
get_issue_details - Added
get_sentry_resource - Removed
get_trace_details
13 tool updates
- First observed
analyze_issue_with_seer - First observed
find_organizations - First observed
find_projects - First observed
find_releases - First observed
find_teams - First observed
get_event_attachment - First observed
get_issue_details - First observed
get_issue_tag_values - First observed
get_trace_details - First observed
search_events - First observed
search_issue_events - First observed
search_issues - First observed
whoami
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
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!
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Related MCP Servers
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables retrieving and analyzing Sentry issues, including stacktraces and debugging information.2-
Sentry MCPofficial
AlicenseAqualityAmaintenanceA remote Model Context Protocol server acting as middleware to the Sentry API, allowing AI assistants like Claude to access Sentry data and functionality through natural language interfaces.745837MIT- FlicenseBqualityFmaintenanceA Model Context Protocol server that enables AI assistants to interact with Sentry for error tracking and monitoring, allowing retrieval and analysis of error data, project management, and performance monitoring through the Sentry API.1121-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap between search_events and search_issues, as both handle issue-related queries, which could cause confusion. However, their descriptions clarify that search_events is for counts/statistics and individual events, while search_issues is for grouped issue lists, helping to mitigate misselection.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case, such as find_organizations, get_sentry_resource, and search_issues. There are no deviations in naming conventions, making the set predictable and easy to understand.
Tool Count5/5
With 14 tools, the count is well-scoped for Sentry's monitoring and debugging domain. Each tool serves a specific function, from resource retrieval to analysis, without feeling bloated or insufficient for the server's purpose.
Completeness4/5
The toolset covers core Sentry operations like issue analysis, resource fetching, and event searching, but there are minor gaps such as the lack of tools for creating or updating resources (e.g., creating issues or projects). Agents can work around this by using existing tools for read-only and analysis tasks.