Skip to main content
Glama

Sentry

by dev.sentry.mcp
OverviewDiscussionsAdmin

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

TDQS

A4.2/5.0

Scored across 14 tools

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedget_profile_details7 fields changed
      • changedInput schema / properties / end / description
        Previous 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'"
      • changedInput schema / properties / focusOnUserCode / description
        Previous 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."
      • addedInput schema / properties / profileId
        Added value: +{
+  "description": "Transaction profile ID from a profile flamegraph URL",
+  "type": "string"
+}
      • addedInput schema / properties / profileUrl
        Added 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"
+}
      • changedInput schema / properties / profilerId / description
        Previous value: -"Profiler session ID (UUID from Sentry profile data)"New value: +"Continuous profiler session ID"
      • changedInput schema / properties / start / description
        Previous 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'"
      • removedInput schema / required
        Removed value: -[
-  "organizationSlug",
-  "projectSlugOrId",
-  "profilerId",
-  "start",
-  "end"
-]
  2. 1 tool update
    • Changedget_replay_details1 field changed
      • changedInput schema / properties / replayUrl / description
        Previous 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/"
  3. 1 tool update
    • Changedget_replay_details1 field changed
      • addedInput schema / properties / regionUrl
        Added 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."
+}
  4. 2 tool updates
    • Addedget_replay_details
    • Changedget_sentry_resource1 field changed
      • changedInput schema / properties / resourceType / enum
        Previous value: -[
-  "issue",
-  "event",
-  "trace",
-  "breadcrumbs"
-]New value: +[
+  "issue",
+  "event",
+  "trace",
+  "breadcrumbs",
+  "replay"
+]
  5. 1 tool update
    • Addedget_profile_details
  6. 3 tool updates
    • Removedget_issue_details
    • Addedget_sentry_resource
    • Removedget_trace_details
  7. 13 tool updates
    • First observedanalyze_issue_with_seer
    • First observedfind_organizations
    • First observedfind_projects
    • First observedfind_releases
    • First observedfind_teams
    • First observedget_event_attachment
    • First observedget_issue_details
    • First observedget_issue_tag_values
    • First observedget_trace_details
    • First observedsearch_events
    • First observedsearch_issue_events
    • First observedsearch_issues
    • First observedwhoami

Related MCP Connectors

Related MCP Servers

  • MCP Sentry

    MCP-100
    F
    license
    B
    quality
    D
    maintenance
    A 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
    -

  • mcp-sentry

    fastmcp-me
    F
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables retrieving and analyzing Sentry issues, including stacktraces and debugging information.
    2
    -
  • Sentry MCP by getsentry

    Sentry MCPofficial

    getsentry
    A
    license
    A
    quality
    A
    maintenance
    A 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.
    7
    17 npm
    852
    MIT

  • Sentry MCP Server

    codyde
    F
    license
    B
    quality
    F
    maintenance
    A 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.
    11
    21
    -
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources