Connect Sentry to Zed
Give Zed governed access to Sentry’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Sentry to Zed in four steps
Admins approve the server once. Everyone in Zed then gets it through the same governed connection.
- 1
Approve Sentry in Runlayer
Add Sentry from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Zed to Runlayer
Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches Sentry’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Zed setup guide - 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
Use Sentry from Zed
Sentry’s approved tools appear in Zed. Every call is checked against policy and recorded.
Tools
16 Sentry tools in Zed
Runlayer policy decides which of these Zed 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.
Control
What Runlayer can see and stop in Zed
Some controls apply to every client at the gateway. Others depend on what Zed exposes to Runlayer.
Gateway policy (available)
Every Sentry call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.
Frequently asked questions
Connect more