Skip to main content

Connect Sentry to Gumloop

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

Set up

Add Sentry to Gumloop in four steps

Admins approve the server once. Everyone in Gumloop 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 Gumloop to Runlayer

    Users add the Runlayer Plugin to Gumloop by following Runlayer’s setup guide. Gumloop reaches Sentry’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Gumloop 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 Gumloop

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

Tools

16 Sentry tools in Gumloop

Runlayer policy decides which of these Gumloop 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 Gumloop

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

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

Frequently asked questions

Connect more

Find another combination