- [PagerDuty](https://www.pagerduty.com/) /
- [Blog](https://www.pagerduty.com/blog) /
- [Announcements](https://www.pagerduty.com/blog/category/announcements/) /
- Connect Claude to PagerDuty Instantly with Claude Auto-Connect
Antonella Hidalgo MorenoNovember 9, 2026 | 3 min read
This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how PagerDuty’s integration with Claude auto-connect recently announced in EA builds towards this vision.
MCP has quickly become the primary way agents connect to the systems that run modern operations, with more agent traffic reaching production systems every month. That makes authorization one of the most important questions in the stack: who is this agent acting for, and who is deciding it should have access?
PagerDuty is partnering with Anthropic to support Claude auto-connect. Anthropic created the Model Context Protocol and continues to drive it forward, and PagerDuty is excited to be part of that effort.
Connected from day one, with no IdP setup required #
Without managed authorization, bringing AI agents via MCP access to a company with thousands of users means scaling friction. Employees must individually open the connector, sign in, approve consent screens, and repeat the process whenever their connection lapses, resulting in thousands of repetitive sign-in steps across an organization.
With the Claude auto-connect, an administrator turns on the PagerDuty MCP connector for the company once, moving authentication from individual employee pop-up screens to a single centralized decision. From then on, members with a matching PagerDuty account see PagerDuty already connected in Claude, with no sign-in screens or login flows required. When a member is removed from the Claude organization, Claude stops connecting them to PagerDuty automatically.
Why this matters for Teams and Security #
Until now, enterprise-managed auth needed an identity provider that supports it. Not every team has the time or the identity setup for a full IdP integration, and they shouldn’t need one to give engineers safe agent access. Auto-connect removes that friction by making managed authorization a one-time setup, taking just a few minutes instead of an extensive IT project.
By leveraging Enterprise Managed Auth, Claude and PagerDuty MCP customers can benefit from:
- AI Auth at Company Scale: Thousands of responders can interact with PagerDuty in Claude immediately without clicking through sign-in screens.
- Rapid Revocation (“Off means off, quickly”): When a member is removed from your Claude organization, their access to PagerDuty ends automatically at the very next token renewal.
- Individual Audit Accountability: Every action in PagerDuty carries the real employee’s identity and existing account permissions, ensuring audit logs show exactly who performed an action instead of masking activity behind a shared bot account or static API key.
- Strict Scope Control: IT administrators specify the exact scopes allowed once, ensuring Claude performs only the actions approved by the company when invoking the PD MCP Server.
Paving the path to autonomous operations #
Your team shouldn’t have to stop and complete a sign-in workflow before an agent can help with an incident. Responders can now pull up PagerDuty in Claude immediately, eliminating handoffs and reducing time spent chasing operational information.
PagerDuty’s approach to autonomous operations:
- Puts intelligent agents to work at scale, handling the noise, accelerating resolution, and keeping you in the loop where it matters
- Deepens the full incident management lifecycle by empowering teams to resolve incidents faster
- Broadens the platform and ecosystem with capabilities that help teams prevent incidents from happening
Claude auto-connect moves us closer to that vision. Ready to connect your whole team to PagerDuty from Claude?
https://www.pagerduty.com/early-access/ Early Access feature, not currently within PagerDuty’s FedRAMP in-scope services.