Unable to use PagerDuty plugin in Cursor Automation

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

I get the same error when trying to setup a Cursor automation that uses the PagerDuty plugin/MCP:

Failed to disconnect PagerDuty Error: Failed to disconnect PagerDuty: 401 {"error":{"message":"User not authorized for this team","details":[{"error":"ERROR_UNAUTHORIZED","details":{"title":"Unauthorized request.","detail":"User not authorized for this team","isRetryable":false,"additionalInfo":{},"buttons":[],"planChoices":[],"analyticsMetadata":{"actionRequired":"login"}},"isExpected":true}]}}

Steps to Reproduce

Setup a Cursor automation that uses the PagerDuty plug in

Expected Behavior

It works and does not error out.

Operating System

MacOS

Version Information

Version: 3.26.16 (Universal)
VS Code Extension API: 1.128.0
Commit: 8fcb8ace5c73fa31f2e2707fd6783160e4ed3e40
Date: 2026-10-21T09:02:57.211Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.11.16
Chromium: 148.0.7778.280
Node.js: 24.19.0
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

Additional Information

It works fine in Cursor on my laptop, so I don’t understand why it’s not working in the browser.

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Jake.Capra,

The PagerDuty plugin in the desktop app and PagerDuty in web Automations are two separate connections. The desktop plugin connects to PagerDuty on its own. Automations on the web use your Cursor team’s shared PagerDuty integration, which only a team admin can connect or disconnect. That’s why Disconnect returns “User not authorized for this team” for your account.

The team’s existing PagerDuty connection is no longer accepted by PagerDuty, so saving an automation that uses it fails. To fix it, ask one of your Cursor team admins to:

  1. Open the Cursor dashboard and go to Integrations.
  2. Click Disconnect on the PagerDuty row.
  3. Click Connect for PagerDuty and finish the PagerDuty sign-in.

Disconnecting also clears the PagerDuty webhook setup for the team’s existing PagerDuty automations, so open and save each of those again after reconnecting. After that, you should be able to save your automation with the PagerDuty trigger.

If it still fails after an admin reconnects, reply here with the exact error you see when saving.