MCP Gateway · Cursor
Connect PagerDuty to Cursor
Code changes affect the people who get paged for them. Cursor can show who is on call before you merge something risky, which PagerDuty service a code path belongs to, and how that service groups its alerts. Cursor hooks send each prompt and tool call to Speakeasy before they run, and fail closed.
- Category
- Infrastructure
- Tools
- 64
- Authentication
- API key
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run PagerDuty MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every PagerDuty call inspected and logged.
Set up
Add PagerDuty to Cursor in 4 steps
- 01
Add PagerDuty from the catalog
An admin finds PagerDuty in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
PagerDuty authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use PagerDuty
Give teams the
mcp:connectscope on the PagerDuty server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds PagerDuty to their gateway on the next call, and removing it takes it away. - 03
Connect Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use PagerDuty from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, PagerDuty's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with PagerDuty
Check who is on call before merging
Before merging a risky change, ask Cursor who is on call for the affected service right now, so you can warn them or wait for a better time.
Find the service behind a code path
Cursor lists PagerDuty services and opens the details of the one that matches the module you're editing, so you know where its alerts go.
Tune alert grouping for a noisy service
If a new log line will trigger many alerts, Cursor reviews the service's alert grouping settings and updates them so responders get one incident, not dozens.
Tools
64 tools
Each PagerDuty tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
list_alert_grouping_settings
List all alert grouping settings with optional filtering.
get_alert_grouping_setting
Get details for a specific alert grouping setting.
list_alerts_from_incident
List alerts for a specific incident.
get_alert_from_incident
Get a specific alert from an incident.
list_change_events
List all change events with optional filtering.
get_change_event
Get details about a specific change event.
Control
What Speakeasy can see and stop in Cursor
The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.
Tool logs
Gateway
Every PagerDuty call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the PagerDuty tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to PagerDuty can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Is PagerDuty activity in Cursor tied to a developer?
Can PagerDuty use in Cursor be stopped at a budget?
How do Cursor users get PagerDuty?
Are PagerDuty calls from Cursor logged?
Connect more