Skip to main content
Book a demo

Connect Sentry to GitHub Copilot

Give GitHub Copilot governed access to Sentry’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot setup guide

Set up

Add Sentry to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Approve Sentry in Runlayer

    Add Sentry from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Sentry’s 16 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Sentry

    Sign in the way Sentry requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Sentry from GitHub Copilot

    Sentry’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.

Tools

16 Sentry tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 4 read data only.

  • Analyze issue with seer

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

  • Execute Sentry tool

    Execute an available Sentry MCP tool discovered through search_sentry_tools.

  • 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

    Find organizations that the user has access to in Sentry.

  • Find projects

    Find projects in Sentry.

  • Get Sentry resource

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

  • Search errors

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

  • Search events

    Search Sentry events and replays.

See all 16 Sentry tools

Control

What Runlayer can see and stop in GitHub Copilot

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.

  • Gateway policy (available)

    Every Sentry call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination