Skip to main content
Book a demo

Sentry

Find the errors behind a bug report and let Seer suggest the root cause.

Book a demo View documentation

Tools

16 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

16 tools found.

  • Analyze issue with seer

    Tool name: analyze_issue_with_seer

    Use Seer to analyze production errors and get detailed root cause analysis with specific code fixes.

  • Execute Sentry tool

    Tool name: execute_sentry_tool

    Execute an available Sentry MCP tool discovered through search_sentry_tools.

  • Find dropped events

    Tool name: find_dropped_events

    Find events dropped before they were stored in Sentry — ground-truth data-fidelity information about what was and wasn't captured.

  • Find organizations

    Read only

    Tool name: find_organizations

    Find organizations that the user has access to in Sentry.

  • Find projects

    Read only

    Tool name: find_projects

    Find projects in Sentry.

  • Get Sentry resource

    Tool name: get_sentry_resource

    Fetch a Sentry resource by URL, or by resourceType plus resourceId.

  • Search errors

    Tool name: search_errors

    Search Sentry error events: exceptions and crashes with stack traces.

  • Search events

    Read only

    Tool name: search_events

    Search Sentry events and replays.

  • Search issues

    Read only

    Tool name: search_issues

    Search for grouped issues/problems in Sentry - returns a LIST of issues, NOT counts or aggregations.

  • Search logs

    Tool name: search_logs

    Search Sentry logs: application log entries, including error- and warning-severity log messages.

  • Search metrics

    Tool name: search_metrics

    Search Sentry metrics: counters, gauges, and distributions, as rows or aggregates.

  • Search profiles

    Tool name: search_profiles

    Search Sentry profiles: transaction and continuous profile results, profile IDs, and profiled transactions.

  • Search replays

    Tool name: search_replays

    Search Sentry session replays: rage clicks, dead clicks, visited pages, errors seen, and replay users.

  • Search Sentry tools

    Tool name: search_sentry_tools

    Search the available Sentry MCP tool catalog by name and description.

  • Search traces

    Tool name: search_traces

    Search Sentry spans and traces: requests, API/HTTP calls, endpoints, DB queries, AI/LLM calls, and other operations.

  • Update issue

    Tool name: update_issue

    Update a Sentry issue's status or assignment.

Compatibility

Connect Sentry to the clients your teams already use

27 AI clients can connect to Sentry through Runlayer. Pick one for its setup steps and controls.

CursorVS CodeClaudeClaude CodeClaude CoworkChatGPTWindsurfGooseCodexHermesGumloopRaycastWarpGitHub CopilotGitHub Copilot CLIMicrosoft 365 CopilotGemini CLIZedCline CLIAntigravityOpenCodeCrushGleanLovablePerplexityECAOh My Pi

Why Runlayer

Why connect Sentry through Runlayer?

One approved path

Approve Sentry once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions