Add a PagerDuty MCP tab alongside PagerDuty API#426
Closed
socialyadept wants to merge 1 commit into
Closed
Conversation
PagerDuty now offers its own hosted MCP server, so this adds a second tab documenting that native option (per-user OAuth via a manually registered Scoped OAuth app, since PagerDuty's server doesn't support dynamic client registration, plus an API key / user token fallback), matching the two-tab pattern already used for Notion. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
![C1 Squire [DEV]](https://avatars.githubusercontent.com/in/2846581?s=40&u=9dfdc6298bb22a241aaf41a6558bc1563c5c6466&v=4){kind=avatar}
Contributor
Author
|
Superseded by #427 — combining all the native-MCP-tab PRs into a single PR per request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PagerDuty ships its own hosted MCP server (
mcp.pagerduty.com) in addition to the REST API C1 already wraps as an MCP server. This adds a second tab to the PagerDuty setup page so admins can tell the two apart and set up either one:Token token=authorization format. Listed as plain PagerDuty in the MCP server catalog.A comparison table above the tabs explains the difference up front (who hosts the server, authentication, access scoping, tool surface, setup effort), and the intro/recommendation prose is explicit about which catalog entry ("PagerDuty" vs "PagerDuty API") each option maps to.
Test plan
/product/admin/mcp-servers#...,/product/admin/enable-ai-access-management#..., etc.) are unchanged from existing usage onmainTabs/Tab/Steps/Step/Note) are balanced🤖 Generated with Claude Code