sentry-mcp-queries

Query Sentry errors via MCP for triage and root-cause analysis.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MajorLift/metamask-extension-skills --skill sentry-mcp-queries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-mcp-queries
Source: https://github.com/MajorLift/metamask-extension-skills/tree/main/domains/analytics/skills/sentry-mcp-queries
Command: npx skills add https://github.com/MajorLift/metamask-extension-skills --skill sentry-mcp-queries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and investigate Sentry errors quickly by querying MCP to surface root causes, error distributions, and recoverable insights.

Core Features & Use Cases

  • Error triage and root-cause analysis using MCP
  • Distribution and release comparison across MV3/MV2
  • Volume estimation and replay retrieval for post-event investigation

Quick Start

Run an MCP query to locate a Sentry issue, inspect its dist distribution, and retrieve a replay or profiling data for analysis.

Frequently Asked Questions about sentry-mcp-queries

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is Sentry MCP error triage and when do I need it?

Sentry MCP error triage queries the Sentry platform to surface root causes and error distributions during production-error investigations. You need it to quickly locate issues and inspect distributions without manual console searches.

How do I check MV3 and MV2 distribution across Sentry releases?

You check MV3 and MV2 distribution by running standardized MCP-based search commands to inspect tag values and compare releases. This surfaces distribution differences to identify extension-specific deployment issues.

Can I retrieve Sentry replay and profiling data using MCP queries?

Yes, you can retrieve Sentry replay and profiling data using standardized MCP commands. The queries access replay and profile information for post-event investigation to help recover contextual session insights.

Does Sentry MCP work for production error volume estimation?

Sentry MCP works for volume estimation by querying error distributions during production-error investigations. It aggregates tag-value inspections to estimate error volumes across targeted releases and distributions.

How do I investigate Sentry root causes using MCP search?

You investigate Sentry root causes by executing MCP-based search commands to locate the specific issue, then inspecting its tag values and distribution data. This surfaces recoverable insights for targeted analysis.

What's the best way to compare Sentry releases for error triage?

The best way to compare Sentry releases for error triage is using standardized MCP commands to query distribution differences and inspect tag values. This surfaces root causes and recoverable insights across MV3 and MV2 releases.