# Connect Sentry to Devin Oncall > Connect Sentry to Devin's Oncall to investigate alerts, bugs, and incidents. Give Devin access to Sentry context to help it investigate active issues, propose code fixes, and help with incidents affecting production. **URL:** https://sentry.io/cookbook/devin-oncall-sentry/ --- Give Devin access to Sentry context to help it investigate active issues, propose code fixes, and help with incidents affecting production. **Time:** ~5 minutes | **Difficulty:** Beginner ## What You'll Learn - Introduced Devin Oncall for investigating and resolving bugs using Sentry data - Installed the Sentry plugin so Devin can read issues, stack traces, breadcrumbs, and Seer RCAs - Created a responder for active Sentry issues and alerts - Enabled Devin to assist with active incidents using Sentry data **Topics:** Issues, Alerts, Error Monitoring, Sentry MCP ## Before you start **Accounts & access** - A [Sentry account](https://sentry.io/signup/) with at least one project receiving errors - A [Devin](https://devin.ai/) organization with access to the Oncall panel **Knowledge** - Basic familiarity with the [Sentry MCP server](https://mcp.sentry.dev) and MCP connectors in Devin ## Steps ### 1. Get started with Devin Oncall Devin Oncall is a way for organizations to automatically deploy Devin to investigate and help resolve issues. By connecting Devin Oncall to Sentry, you gain a powerful new debugging assistant that helps you respond to issues in real time. Sentry supports Devin Oncall with: - **Alerts & Bugs**: Have Devin investigate application alerts or active bugs as they are detected in Sentry. Give Devin access to Sentry context through the Sentry plugin. - **Incidents**: Automatically add Devin to incident channels when they get created and use Sentry as the primary data source for gathering information about the incident-causing issue. [Learn more about Devin Oncall](https://docs.devin.ai/product-guides/devin-oncall) ### 2. Install the Sentry plugin Ensure that Devin has access to your Sentry projects using the Sentry plugin. The plugin includes access to the Sentry MCP server and can be installed for your entire organization or by individual users. You can even make sure the MCP server is installed for everyone by default. To set up the plugin, go to **Customize** -> Select **Browse Marketplace** -> Search for **Sentry** -> Install and authenticate [Learn more about the Sentry MCP server](https://mcp.sentry.dev) ### 3. Create a responder for alerts & bugs Devin Oncall lets organizations determine which alerts or active bugs they want Devin to investigate and then Devin can use the Sentry MCP server to triage those bugs using relevant Sentry information like: - **[Stack traces & breadcrumbs](https://docs.sentry.io/product/sentry-basics/getting-started-tutorial/enable-readable-stack-traces/)** - **[Tracing & spans](https://docs.sentry.io/product/trace-explorer/)** - **[Logs](https://docs.sentry.io/product/logs/)** - **[Application metrics](https://docs.sentry.io/product/metrics/)** - **[Session Replays](https://docs.sentry.io/product/session-replay/)** [What context Sentry captures on an issue](https://docs.sentry.io/product/issues/issue-details/) ### 4. Deploy Devin with Sentry for incidents No more weekend pages being sent to your engineers. Instead you can set up Devin Oncall to automatically include Devin in incident responses and resolve issues using Sentry data. Devin can be automatically deployed into incident Slack channels, configured to be more proactive or reactive resolving issues, and you can configure which modes you want Devin to run in at various stages of the incident response. [Ensure you send the right data to Sentry](https://docs.sentry.io/product/sentry-basics/) ## Summary **Help Devin debug better with Sentry context.** Give Devin access to Sentry context to help it investigate active issues, propose code fixes, and help with incidents affecting production. ## Pro Tips - Authenticate the Sentry connection with a dedicated user whose organization role and team membership cover only the projects Devin should investigate. - Connect your repositories in Sentry so Seer and Devin can reason over your actual source code, not just telemetry. - Start responders on one or two high-signal projects, then widen the scope once you trust the results. ## Common Pitfalls - Pointing a responder at every alert. Each investigation spends Devin ACUs, so scope responders to issues and incidents that matter. - Treating alert text as instructions. Issue titles and payloads are untrusted input; let Devin investigate the issue itself. - Forgetting the Sentry MCP can write. It can update issue status, assignments, tags, and alerts with the permissions of the account you connect. ## FAQ **Do I need to install anything to use the Sentry MCP server?** No. Sentry hosts and manages a remote MCP server with OAuth authentication. You just add the URL to your client and log in. **Do I need a paid Sentry plan to use the MCP server?** No. The Sentry MCP server works with any Sentry plan, including the free tier. Access to specific data (e.g. longer retention windows, Seer root-cause analysis) depends on your plan, but the core issue-fetching and log-reading tools are available to all users. **Does the Sentry MCP server cost extra or use my event quota?** No. The Sentry MCP server is free and only works with data you already have in Sentry, so it doesn't send new events or count against your event quota. Seer usage itself is billed separately; see Sentry's pricing for current Seer details. **What can I ask the MCP server besides fixing issues?** The MCP server provides over 16 tools. You can query issues, search for errors across files and projects, check releases, look up project DSNs, investigate performance data through traces and spans, and trigger Seer analysis, all through natural language prompts. **What does Seer need to generate a good root-cause analysis?** Seer works best with a GitHub repository connected in your [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/). With a linked codebase it can point to the exact culprit lines and generate a concrete fix; without one, it still reasons over your issue details, traces, logs, and profiles to explain the likely root cause. ## Next Steps - [product/error-monitoring](https://sentry.io/product/error-monitoring/) - [product/seer](https://sentry.io/product/seer/) - [Explore the Sentry MCP server](https://mcp.sentry.dev/): See every tool the Sentry MCP server exposes to Devin and other coding agents. --- *Source: [sentry.io/cookbook/devin-oncall-sentry/](https://sentry.io/cookbook/devin-oncall-sentry/)*