Sentry MCP Server

The Sentry MCP Server provides comprehensive integration with Sentry's error tracking and performance monitoring platform, enabling AI assistants to interact with your Sentry data through natural language. This server allows you to search issues and events, analyze errors with AI-powered root cause analysis, manage releases and projects, access documentation, and much more—all without leaving your development environment.

Overview

This MCP server transforms how you interact with Sentry by providing intelligent access to your application monitoring data. Whether you need to investigate production errors, analyze performance traces, retrieve SDK configuration details, or search through Sentry's extensive documentation, this server acts as a bridge between your AI assistant and the Sentry platform. It supports both Sentry's cloud service and self-hosted installations, with automatic region detection for multi-region deployments.

Key Capabilities

User and Organization Management

Quickly identify yourself and discover which organizations and teams you have access to. These foundational tools help establish context for all other operations and ensure you're working with the correct organizational scope.

Project and Release Discovery

Browse projects across your organizations and track releases with detailed version information and deployment history. The release management capabilities make it easy to correlate errors with specific versions and understand when issues were introduced.

Intelligent Issue Search

Search through grouped issues using natural language queries that are automatically translated into Sentry's powerful query syntax. Find issues by status, assignment, user impact, error type, and more without memorizing complex search patterns.

Event and Performance Analysis

Query individual error events, log entries, and performance spans with full support for aggregations and statistics. This is your go-to tool for answering questions like "how many errors occurred today" or "what's the average response time for API calls."

AI-Powered Root Cause Analysis

Leverage Sentry's Seer AI to perform deep analysis of production errors, receiving detailed root cause explanations with specific code fixes and implementation guidance. The analysis includes file locations, line numbers, and step-by-step troubleshooting instructions.

Comprehensive Documentation Access

Search and retrieve Sentry's SDK documentation for any platform or framework. Whether you're setting up a new integration, configuring advanced features, or troubleshooting SDK issues, the documentation tools provide instant access to relevant guides and examples.

Trace and Attachment Support

Access distributed traces for performance analysis and download event attachments like screenshots and log files. These capabilities are essential for understanding complex performance issues and accessing diagnostic artifacts.

Tools

whoami

Identify the authenticated user in Sentry, returning name and email address information.

Parameters: None required

find_organizations

Retrieve all organizations the authenticated user has access to, including organization slugs needed for other API operations.

Parameters: None required

find_teams

List all teams within a specific organization.

Parameters:

organizationSlug (required): The organization's slug
regionUrl (optional): Region-specific URL for cloud deployments

find_projects

Discover all projects within an organization.

Parameters:

organizationSlug (required): The organization's slug
regionUrl (optional): Region-specific URL for cloud deployments

find_releases

Search for releases across projects, with optional query filtering to find specific versions.

Parameters:

organizationSlug (required): The organization's slug
projectSlug (optional): Limit results to a specific project
query (optional): Search string to match against version names
regionUrl (optional): Region-specific URL for cloud deployments

get_issue_details

Retrieve comprehensive information about a specific issue by ID or URL, including stack traces, event details, and metadata.

Parameters:

issueId (optional): Issue identifier like "PROJECT-123"
eventId (optional): Specific event identifier
issueUrl (optional): Full URL to the issue
organizationSlug (optional): Required if using issueId or eventId
regionUrl (optional): Region-specific URL for cloud deployments

get_trace_details

Fetch detailed information about a distributed trace, including span breakdown and performance statistics.

Parameters:

organizationSlug (required): The organization's slug
traceId (required): 32-character hexadecimal trace identifier
regionUrl (optional): Region-specific URL for cloud deployments

get_event_attachment

Download or list attachments associated with a specific event, such as screenshots or log files.

Parameters:

organizationSlug (required): The organization's slug
projectSlug (required): The project's slug
eventId (required): The event identifier
attachmentId (optional): Specific attachment to download; omit to list all attachments
regionUrl (optional): Region-specific URL for cloud deployments

search_events

Search for individual events with support for aggregations and statistics. This is the primary tool for queries involving counts, sums, averages, or individual event listings. Automatically selects the appropriate dataset (errors, logs, or spans) based on your query.

Parameters:

organizationSlug (required): The organization's slug
naturalLanguageQuery (required): Natural language description of the search
projectSlug (optional): Limit results to a specific project
limit (optional): Maximum results to return (1-100, default 10)
includeExplanation (optional): Include query translation explanation
regionUrl (optional): Region-specific URL for cloud deployments

find_dsns

Retrieve DSN (Data Source Name) configuration values for a specific project, needed for SDK setup.

Parameters:

organizationSlug (required): The organization's slug
projectSlug (required): The project's slug
regionUrl (optional): Region-specific URL for cloud deployments

analyze_issue_with_seer

Trigger AI-powered root cause analysis for a specific issue, receiving detailed explanations, code fixes, and troubleshooting guidance. Automatically checks for existing analysis and initiates new analysis if needed.

Parameters:

issueId (optional): Issue identifier like "PROJECT-123"
issueUrl (optional): Full URL to the issue
organizationSlug (optional): Required if using issueId
instruction (optional): Custom guidance for the AI analysis
regionUrl (optional): Region-specific URL for cloud deployments

search_docs

Search Sentry's technical documentation for SDK setup instructions, configuration guides, and integration examples across all supported platforms and frameworks.

Parameters:

query (required): Search query in natural language (2-200 characters)
guide (optional): Filter to specific platform or integration (e.g., "javascript/nextjs", "python/django")
maxResults (optional): Number of results to return (1-10, default 3)

get_doc

Retrieve the full markdown content of a specific Sentry documentation page.

Parameters:

path (required): Documentation path ending in .md (e.g., "/platforms/javascript/guides/nextjs.md")

search_issues

Search for grouped issues using natural language queries. Returns lists of issues with metadata like title, status, and affected user counts. Does not support aggregations or counts—use search_events for statistics.

Parameters:

organizationSlug (required): The organization's slug
naturalLanguageQuery (required): Natural language description of issues to find
projectSlugOrId (optional): Limit to specific project by slug or numeric ID
limit (optional): Maximum results to return (1-100, default 10)
includeExplanation (optional): Include query translation explanation
regionUrl (optional): Region-specific URL for cloud deployments

Prompts

find_errors_in_file

A specialized prompt for discovering errors in Sentry associated with a specific filename, useful for file-centric debugging workflows.

Arguments:

organizationSlug (required): The organization's slug
filename (required): The filename to search for errors

fix_issue_with_seer

A workflow prompt that orchestrates the process of analyzing and fixing an issue using Seer AI, combining issue retrieval with root cause analysis.

Arguments:

organizationSlug (optional): The organization's slug
issueId (optional): Issue identifier like "PROJECT-123"
issueUrl (optional): Full URL to the issue

Resource Templates

sentry-docs-platform

Access Sentry SDK documentation for a specific platform as markdown content.

URI Template: https://docs.sentry.io/platforms/{platform}/

Parameters:

platform: The platform identifier (e.g., "javascript", "python", "java")

MIME Type: text/markdown

sentry-docs-platform-guide

Access integration guides for specific frameworks within a platform as markdown content.

URI Template: https://docs.sentry.io/platforms/{platform}/guides/{framework}/

Parameters:

platform: The platform identifier (e.g., "javascript", "python")
framework: The framework identifier (e.g., "nextjs", "django")

MIME Type: text/markdown

Usage Patterns

When working with this MCP server, you'll typically follow these patterns:

Issue Investigation: Start by searching for issues with search_issues, then drill into specific problems with get_issue_details, and finally use analyze_issue_with_seer for in-depth root cause analysis and fix recommendations.

Performance Analysis: Use search_events with natural language queries to find performance spans, then examine specific traces with get_trace_details to understand the full request flow.

SDK Setup: Search documentation with search_docs to find relevant integration guides, then retrieve complete documentation pages with get_doc for implementation details.

Statistics and Metrics: Use search_events for any questions involving counts, aggregations, or statistics across errors, logs, or performance data.

Project Discovery: Begin with find_organizations to identify available organizations, then use find_projects to discover projects, and find_dsns to retrieve configuration values for SDK integration.

The natural language query capabilities in search_events and search_issues make it easy to ask questions without memorizing Sentry's query syntax, while the AI-powered analysis tools provide actionable insights for resolving production issues quickly.