From c799b15f3d3b308f42f09785780a902f54501c3d Mon Sep 17 00:00:00 2001 From: Eric Gustin Date: Fri, 16 Oct 2026 15:01:30 -0700 Subject: [PATCH 1/3] docs(pagerduty): add the PagerDuty integration guide sections PagerDuty's Integration Directory review asks for an integration guide that follows its template and has a support section. Add curation chunks that give the PagerDuty toolkit page those sections: benefits, how it works, requirements, support, an integration walkthrough (install in PagerDuty, set up in Arcade), and how to uninstall. - Replace the two top callouts, which told every reader to register their own Scoped OAuth app, with one that sends Arcade Cloud users to the walkthrough and keeps the own-app guidance for self-hosted deployments and agents built for people outside the project. - Drop the auth chunk, which repeated the auth provider page and pointed at scopes "shown above". - Write the support address with a before the @ so Cloudflare's email obfuscation doesn't turn it into a link that 404s for crawlers. - Re-sync pagerduty.json (documentationChunks and curationSourceHash only) so the preview deploy shows the page. --- .../chunks/001-description-after-warning.mdx | 11 ---- .../chunks/002-description-after-info.mdx | 9 +++- .../chunks/003-auth-after-markdown.mdx | 10 ---- .../chunks/004-integration-benefits.mdx | 15 ++++++ .../pagerduty/chunks/005-how-it-works.mdx | 18 +++++++ .../pagerduty/chunks/006-requirements.mdx | 16 ++++++ .../curation/pagerduty/chunks/007-support.mdx | 15 ++++++ .../chunks/008-integration-walkthrough.mdx | 46 ++++++++++++++++ .../pagerduty/chunks/009-how-to-uninstall.mdx | 23 ++++++++ .../data/toolkits/pagerduty.json | 52 ++++++++++++++++--- 10 files changed, 184 insertions(+), 31 deletions(-) delete mode 100644 toolkit-docs-generator/curation/pagerduty/chunks/001-description-after-warning.mdx delete mode 100644 toolkit-docs-generator/curation/pagerduty/chunks/003-auth-after-markdown.mdx create mode 100644 toolkit-docs-generator/curation/pagerduty/chunks/004-integration-benefits.mdx create mode 100644 toolkit-docs-generator/curation/pagerduty/chunks/005-how-it-works.mdx create mode 100644 toolkit-docs-generator/curation/pagerduty/chunks/006-requirements.mdx create mode 100644 toolkit-docs-generator/curation/pagerduty/chunks/007-support.mdx create mode 100644 toolkit-docs-generator/curation/pagerduty/chunks/008-integration-walkthrough.mdx create mode 100644 toolkit-docs-generator/curation/pagerduty/chunks/009-how-to-uninstall.mdx diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/001-description-after-warning.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/001-description-after-warning.mdx deleted file mode 100644 index 078ddeb44..000000000 --- a/toolkit-docs-generator/curation/pagerduty/chunks/001-description-after-warning.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -type: warning -location: description -position: after ---- - - Register a **Scoped OAuth** PagerDuty app with the scopes listed in the - [PagerDuty auth provider](/references/auth-providers/pagerduty#permissions). - Classic OAuth apps don't support the per-resource scopes these tools - request. - diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/002-description-after-info.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/002-description-after-info.mdx index ad4dde867..2f3ae0453 100644 --- a/toolkit-docs-generator/curation/pagerduty/chunks/002-description-after-info.mdx +++ b/toolkit-docs-generator/curation/pagerduty/chunks/002-description-after-info.mdx @@ -4,6 +4,11 @@ location: description position: after --- - Configure PagerDuty OAuth in the [PagerDuty auth - provider](/references/auth-providers/pagerduty) before using these tools. + On Arcade Cloud, these tools use Arcade's PagerDuty app, which a PagerDuty + administrator installs once per account. See the [integration + walkthrough](#integration-walkthrough). If you self-host the Arcade Engine, or + you're building an agent for people who aren't members of your Arcade + project, register your own **Scoped OAuth** app and configure the [PagerDuty + auth provider](/references/auth-providers/pagerduty). Classic OAuth apps + don't support the per-resource scopes these tools request. diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/003-auth-after-markdown.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/003-auth-after-markdown.mdx deleted file mode 100644 index c0e1a45bd..000000000 --- a/toolkit-docs-generator/curation/pagerduty/chunks/003-auth-after-markdown.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -type: markdown -location: auth -position: after ---- -PagerDuty requires OAuth2. Configure the PagerDuty auth provider and request the scopes shown above per tool. Tokens are passed as Bearer auth: -``` -Authorization: Bearer -``` -See PagerDuty auth docs: [PagerDuty API Authentication](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTYz-authentication). diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/004-integration-benefits.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/004-integration-benefits.mdx new file mode 100644 index 000000000..bc0f6f805 --- /dev/null +++ b/toolkit-docs-generator/curation/pagerduty/chunks/004-integration-benefits.mdx @@ -0,0 +1,15 @@ +--- +type: markdown +location: custom_section +position: after +header: "## PagerDuty + Arcade integration benefits" +priority: 10 +--- +## PagerDuty + Arcade integration benefits + +- **Triage incidents from your AI agent.** List incidents filtered by status, urgency, service, team, or time, read an incident's details and log entries, then acknowledge, resolve, reopen, or reassign it without leaving the agent. +- **Find out who's on call.** Query on-call entries, schedules, and escalation policies to see who's responsible for a service and how PagerDuty escalates its incidents. +- **Look up the people and services involved.** Search users by name or email, and read teams, their members, and services. +- **Use the agent you already have.** The tools work in any MCP client that connects to an Arcade MCP gateway, such as Claude, Cursor, or VS Code, and in agents you build with the Arcade SDKs. +- **Request only the access each tool needs.** Each tool asks for the narrowest PagerDuty OAuth scopes for its job and acts as the PagerDuty user who authorized it. +- **Keep credentials away from the model.** Arcade stores each user's PagerDuty token and calls PagerDuty on the server, so the token never reaches the language model. diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/005-how-it-works.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/005-how-it-works.mdx new file mode 100644 index 000000000..d7ba99cea --- /dev/null +++ b/toolkit-docs-generator/curation/pagerduty/chunks/005-how-it-works.mdx @@ -0,0 +1,18 @@ +--- +type: markdown +location: custom_section +position: after +header: "## How it works" +priority: 20 +--- +## How it works + +The Arcade PagerDuty MCP server provides tools that call the [PagerDuty REST API](https://docs.pagerduty.com/developer/api/reference) as the PagerDuty user who authorized them. + +1. An agent calls a PagerDuty tool through Arcade, for example from an MCP client connected to an Arcade MCP gateway. +2. If the user hasn't authorized PagerDuty yet, Arcade returns an authorization link instead of a result. The user opens the link, signs in to PagerDuty, and approves Arcade's PagerDuty app on PagerDuty's consent screen. +3. Arcade stores the user's token, calls PagerDuty with it, and returns the result to the agent. Later calls reuse the stored authorization. + +Each tool can only do what both its scopes and the user's PagerDuty permissions allow, and PagerDuty records its actions as that user's. Arcade refreshes the token when it expires. Once PagerDuty's refresh window runs out, the next tool call asks the user to authorize again. See PagerDuty's [token lifetimes](https://docs.pagerduty.com/developer/private-apps#token-lifetimes). + +The tools only act when an agent calls them. The integration doesn't send events to PagerDuty, create incidents, or receive webhooks, so it doesn't need a PagerDuty service integration or an integration key. diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/006-requirements.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/006-requirements.mdx new file mode 100644 index 000000000..ef88ffd97 --- /dev/null +++ b/toolkit-docs-generator/curation/pagerduty/chunks/006-requirements.mdx @@ -0,0 +1,16 @@ +--- +type: markdown +location: custom_section +position: after +header: "## Requirements" +priority: 30 +--- +## Requirements + +- **A PagerDuty account with Arcade's PagerDuty app installed.** A PagerDuty administrator installs the app once for the whole account. See the [integration walkthrough](#integration-walkthrough). +- **An Arcade account that's a member of your Arcade project.** Create an Arcade account if you don't have one. +- **An MCP client**, such as Claude, Cursor, or VS Code. You can also try the tools in the Arcade dashboard's Playground without one. + +Each user authorizes with their own PagerDuty account, so the tools can only do what that user's PagerDuty role allows. + +If you self-host the Arcade Engine, or you're building an agent for people who aren't members of your Arcade project, register your own Scoped OAuth app instead. See the [PagerDuty auth provider](/references/auth-providers/pagerduty). diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/007-support.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/007-support.mdx new file mode 100644 index 000000000..c0423fe4c --- /dev/null +++ b/toolkit-docs-generator/curation/pagerduty/chunks/007-support.mdx @@ -0,0 +1,15 @@ +--- +type: markdown +location: custom_section +position: after +header: "## Support" +priority: 40 +--- +## Support + +For help with the Arcade PagerDuty integration: + +- Customers on paid plans can email Arcade support at support@arcade.dev. +- Anyone can ask in the [Arcade Discord community](https://discord.gg/GUZEMpEZ9p). + +The [Arcade contact page](/resources/contact-us) lists every support channel. diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/008-integration-walkthrough.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/008-integration-walkthrough.mdx new file mode 100644 index 000000000..eaa75478f --- /dev/null +++ b/toolkit-docs-generator/curation/pagerduty/chunks/008-integration-walkthrough.mdx @@ -0,0 +1,46 @@ +--- +type: markdown +location: custom_section +position: after +header: "## Integration walkthrough" +priority: 50 +--- +## Integration walkthrough + +### In PagerDuty + +A PagerDuty administrator installs Arcade's PagerDuty app once for the whole account. Until then, nobody in the account can authorize it. + +1. Sign in to PagerDuty as a user with the Admin or Account Owner role. +2. Go to `https://.pagerduty.com/oauth-apps/PHRMXL1`, where `` is the first part of your PagerDuty web address. +3. Review the app details and the scopes it requests, then click **Install on your account**. + +If you aren't an administrator, open the same page and click **Copy install link** to send the link to one. + +Installing the app doesn't grant access on its own. Each user authorizes Arcade the first time they use a PagerDuty tool. Arcade doesn't use PagerDuty's Events API, so you don't need to add an integration to a service or copy an integration key. + +### In Arcade + +**1. Create an MCP gateway with the PagerDuty tools** + +1. Sign in to the [Arcade dashboard](https://app.arcade.dev) and select **MCP gateways**. +2. Click **Create MCP gateway**. +3. Under **Name it**, enter a name such as `PagerDuty`. +4. Under **Select apps**, find **PagerDuty** and select it to add all of its tools. +5. Under **Choose who connects**, select **Members of this Project**. +6. Click **Create MCP gateway**. + +For the other gateway options, see [Create via Dashboard](/operate/governance/mcp-gateways/create-via-dashboard). + +**2. Connect your MCP client** + +In the **MCP gateways** list, open the gateway's actions menu, select **Connect to client**, and follow the steps for your client. [Connect to MCP Clients](/get-started/mcp-clients) has a guide for each supported client. + +**3. Authorize PagerDuty** + +1. Ask your agent a PagerDuty question, such as "Which PagerDuty incidents are open right now?" +2. The first PagerDuty tool call returns an authorization link. Open it, and sign in to Arcade if prompted. +3. Sign in to PagerDuty, review the requested scopes, and click **Submit Consent**. +4. Return to your agent. If it doesn't continue on its own, ask again. + +To try the tools without an MCP client, open **Playground** in the Arcade dashboard, click **Select Tools**, add the PagerDuty tools, and ask the same question. diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/009-how-to-uninstall.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/009-how-to-uninstall.mdx new file mode 100644 index 000000000..ba27e3412 --- /dev/null +++ b/toolkit-docs-generator/curation/pagerduty/chunks/009-how-to-uninstall.mdx @@ -0,0 +1,23 @@ +--- +type: markdown +location: custom_section +position: after +header: "## How to uninstall" +priority: 60 +--- +## How to uninstall + +Remove the integration in both Arcade and PagerDuty. Revoking a connection in Arcade deletes the token Arcade stores, but it doesn't revoke the authorization in PagerDuty. + +### In Arcade + +- **Remove the tools from your gateway.** In **MCP gateways**, open the gateway's actions menu and select **Edit gateway**. Under **Select apps**, clear **PagerDuty**, then click **Save changes**. To remove the whole gateway, select **Delete gateway** instead. +- **Delete stored authorizations.** Go to **Connections** > **Connected users**, filter the list to the PagerDuty provider, and click **Revoke** on each connection. Revoking requires the Admin or Member project role. + +### In PagerDuty + +Go to **Integrations** > **OAuth Apps** and select **Arcade.dev**. Then: + +- **To revoke your own access**, click **Revoke Your User Token**. +- **To revoke every user's access** (administrators only), click **Revoke All User Tokens**. Each user must authorize again to keep using the tools. +- **To remove the app from your account** (administrators only), click **Uninstall**. This revokes every user's token, and nobody can authorize the app again until an administrator reinstalls it. diff --git a/toolkit-docs-generator/data/toolkits/pagerduty.json b/toolkit-docs-generator/data/toolkits/pagerduty.json index 00ef69fa9..6dbdcd469 100644 --- a/toolkit-docs-generator/data/toolkits/pagerduty.json +++ b/toolkit-docs-generator/data/toolkits/pagerduty.json @@ -1425,27 +1425,63 @@ ], "documentationChunks": [ { - "type": "warning", + "type": "info", "location": "description", "position": "after", - "content": "\n Register a **Scoped OAuth** PagerDuty app with the scopes listed in the\n [PagerDuty auth provider](/references/auth-providers/pagerduty#permissions).\n Classic OAuth apps don't support the per-resource scopes these tools\n request.\n" + "content": "\n On Arcade Cloud, these tools use Arcade's PagerDuty app, which a PagerDuty\n administrator installs once per account. See the [integration\n walkthrough](#integration-walkthrough). If you self-host the Arcade Engine, or\n you're building an agent for people who aren't members of your Arcade\n project, register your own **Scoped OAuth** app and configure the [PagerDuty\n auth provider](/references/auth-providers/pagerduty). Classic OAuth apps\n don't support the per-resource scopes these tools request.\n" }, { - "type": "info", - "location": "description", + "type": "markdown", + "location": "custom_section", + "position": "after", + "content": "## PagerDuty + Arcade integration benefits\n\n- **Triage incidents from your AI agent.** List incidents filtered by status, urgency, service, team, or time, read an incident's details and log entries, then acknowledge, resolve, reopen, or reassign it without leaving the agent.\n- **Find out who's on call.** Query on-call entries, schedules, and escalation policies to see who's responsible for a service and how PagerDuty escalates its incidents.\n- **Look up the people and services involved.** Search users by name or email, and read teams, their members, and services.\n- **Use the agent you already have.** The tools work in any MCP client that connects to an Arcade MCP gateway, such as Claude, Cursor, or VS Code, and in agents you build with the Arcade SDKs.\n- **Request only the access each tool needs.** Each tool asks for the narrowest PagerDuty OAuth scopes for its job and acts as the PagerDuty user who authorized it.\n- **Keep credentials away from the model.** Arcade stores each user's PagerDuty token and calls PagerDuty on the server, so the token never reaches the language model.", + "header": "## PagerDuty + Arcade integration benefits", + "priority": 10 + }, + { + "type": "markdown", + "location": "custom_section", + "position": "after", + "content": "## How it works\n\nThe Arcade PagerDuty MCP server provides tools that call the [PagerDuty REST API](https://docs.pagerduty.com/developer/api/reference) as the PagerDuty user who authorized them.\n\n1. An agent calls a PagerDuty tool through Arcade, for example from an MCP client connected to an Arcade MCP gateway.\n2. If the user hasn't authorized PagerDuty yet, Arcade returns an authorization link instead of a result. The user opens the link, signs in to PagerDuty, and approves Arcade's PagerDuty app on PagerDuty's consent screen.\n3. Arcade stores the user's token, calls PagerDuty with it, and returns the result to the agent. Later calls reuse the stored authorization.\n\nEach tool can only do what both its scopes and the user's PagerDuty permissions allow, and PagerDuty records its actions as that user's. Arcade refreshes the token when it expires. Once PagerDuty's refresh window runs out, the next tool call asks the user to authorize again. See PagerDuty's [token lifetimes](https://docs.pagerduty.com/developer/private-apps#token-lifetimes).\n\nThe tools only act when an agent calls them. The integration doesn't send events to PagerDuty, create incidents, or receive webhooks, so it doesn't need a PagerDuty service integration or an integration key.", + "header": "## How it works", + "priority": 20 + }, + { + "type": "markdown", + "location": "custom_section", + "position": "after", + "content": "## Requirements\n\n- **A PagerDuty account with Arcade's PagerDuty app installed.** A PagerDuty administrator installs the app once for the whole account. See the [integration walkthrough](#integration-walkthrough).\n- **An Arcade account that's a member of your Arcade project.** Create an Arcade account if you don't have one.\n- **An MCP client**, such as Claude, Cursor, or VS Code. You can also try the tools in the Arcade dashboard's Playground without one.\n\nEach user authorizes with their own PagerDuty account, so the tools can only do what that user's PagerDuty role allows.\n\nIf you self-host the Arcade Engine, or you're building an agent for people who aren't members of your Arcade project, register your own Scoped OAuth app instead. See the [PagerDuty auth provider](/references/auth-providers/pagerduty).", + "header": "## Requirements", + "priority": 30 + }, + { + "type": "markdown", + "location": "custom_section", + "position": "after", + "content": "## Support\n\nFor help with the Arcade PagerDuty integration:\n\n- Customers on paid plans can email Arcade support at support@arcade.dev.\n- Anyone can ask in the [Arcade Discord community](https://discord.gg/GUZEMpEZ9p).\n\nThe [Arcade contact page](/resources/contact-us) lists every support channel.", + "header": "## Support", + "priority": 40 + }, + { + "type": "markdown", + "location": "custom_section", "position": "after", - "content": "\n Configure PagerDuty OAuth in the [PagerDuty auth\n provider](/references/auth-providers/pagerduty) before using these tools.\n" + "content": "## Integration walkthrough\n\n### In PagerDuty\n\nA PagerDuty administrator installs Arcade's PagerDuty app once for the whole account. Until then, nobody in the account can authorize it.\n\n1. Sign in to PagerDuty as a user with the Admin or Account Owner role.\n2. Go to `https://.pagerduty.com/oauth-apps/PHRMXL1`, where `` is the first part of your PagerDuty web address.\n3. Review the app details and the scopes it requests, then click **Install on your account**.\n\nIf you aren't an administrator, open the same page and click **Copy install link** to send the link to one.\n\nInstalling the app doesn't grant access on its own. Each user authorizes Arcade the first time they use a PagerDuty tool. Arcade doesn't use PagerDuty's Events API, so you don't need to add an integration to a service or copy an integration key.\n\n### In Arcade\n\n**1. Create an MCP gateway with the PagerDuty tools**\n\n1. Sign in to the [Arcade dashboard](https://app.arcade.dev) and select **MCP gateways**.\n2. Click **Create MCP gateway**.\n3. Under **Name it**, enter a name such as `PagerDuty`.\n4. Under **Select apps**, find **PagerDuty** and select it to add all of its tools.\n5. Under **Choose who connects**, select **Members of this Project**.\n6. Click **Create MCP gateway**.\n\nFor the other gateway options, see [Create via Dashboard](/operate/governance/mcp-gateways/create-via-dashboard).\n\n**2. Connect your MCP client**\n\nIn the **MCP gateways** list, open the gateway's actions menu, select **Connect to client**, and follow the steps for your client. [Connect to MCP Clients](/get-started/mcp-clients) has a guide for each supported client.\n\n**3. Authorize PagerDuty**\n\n1. Ask your agent a PagerDuty question, such as \"Which PagerDuty incidents are open right now?\"\n2. The first PagerDuty tool call returns an authorization link. Open it, and sign in to Arcade if prompted.\n3. Sign in to PagerDuty, review the requested scopes, and click **Submit Consent**.\n4. Return to your agent. If it doesn't continue on its own, ask again.\n\nTo try the tools without an MCP client, open **Playground** in the Arcade dashboard, click **Select Tools**, add the PagerDuty tools, and ask the same question.", + "header": "## Integration walkthrough", + "priority": 50 }, { "type": "markdown", - "location": "auth", + "location": "custom_section", "position": "after", - "content": "PagerDuty requires OAuth2. Configure the PagerDuty auth provider and request the scopes shown above per tool. Tokens are passed as Bearer auth:\n```\nAuthorization: Bearer \n```\nSee PagerDuty auth docs: [PagerDuty API Authentication](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTYz-authentication)." + "content": "## How to uninstall\n\nRemove the integration in both Arcade and PagerDuty. Revoking a connection in Arcade deletes the token Arcade stores, but it doesn't revoke the authorization in PagerDuty.\n\n### In Arcade\n\n- **Remove the tools from your gateway.** In **MCP gateways**, open the gateway's actions menu and select **Edit gateway**. Under **Select apps**, clear **PagerDuty**, then click **Save changes**. To remove the whole gateway, select **Delete gateway** instead.\n- **Delete stored authorizations.** Go to **Connections** > **Connected users**, filter the list to the PagerDuty provider, and click **Revoke** on each connection. Revoking requires the Admin or Member project role.\n\n### In PagerDuty\n\nGo to **Integrations** > **OAuth Apps** and select **Arcade.dev**. Then:\n\n- **To revoke your own access**, click **Revoke Your User Token**.\n- **To revoke every user's access** (administrators only), click **Revoke All User Tokens**. Each user must authorize again to keep using the tools.\n- **To remove the app from your account** (administrators only), click **Uninstall**. This revokes every user's token, and nobody can authorize the app again until an administrator reinstalls it.", + "header": "## How to uninstall", + "priority": 60 } ], "customImports": [], "subPages": [], - "curationSourceHash": "07d907a3da0482c380fb3d61f72187694ccac5f75c2461ccefd4a96be4674274", + "curationSourceHash": "1a945a964740f4fc063301803f29511728f9b3b18be934cc0978ce382d9d6e00", "generatedAt": "2026-10-07T21:25:50.988Z", "summary": "## PagerDuty Toolkit\n\nThe Arcade PagerDuty toolkit lets LLMs interact with PagerDuty to query and manage incidents, on-call schedules, teams, services, and escalation policies.\n\n## Capabilities\n\n- **Incident management** — retrieve, list (with filters for status, urgency, service, team, and time), update status (acknowledge, resolve, reopen), and reassign incidents to specific users.\n- **On-call & scheduling** — list on-call entries, schedules, and escalation policies; fetch individual policies by ID.\n- **Teams, users & services** — list and look up teams (with members and linked resources), users, and services; fuzzy-search users by name or email; retrieve individual records by ID.\n- **Activity feed** — list log entries showing incident triggers, acknowledgments, escalations, and resolutions across the account.\n- **Identity** — retrieve the authenticated user's PagerDuty profile including contact and notification summaries via `Whoami`.\n\n## OAuth\n\nThis toolkit uses OAuth 2.0 via the **PagerDuty** Arcade auth provider. See the [PagerDuty provider docs](https://docs.arcade.dev/en/references/auth-providers/pagerduty) for configuration details." } \ No newline at end of file From 6863eac8045f1142a873418fbe1e37f546ea9eeb Mon Sep 17 00:00:00 2001 From: Eric Gustin Date: Fri, 16 Oct 2026 15:36:13 -0700 Subject: [PATCH 2/3] test(toolkit-docs-generator): count the PagerDuty guide chunks in the curation corpus The PagerDuty guide adds six chunks and removes two, so the checked-in corpus now holds 93 chunks. --- toolkit-docs-generator/tests/scenarios/curation-corpus.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/toolkit-docs-generator/tests/scenarios/curation-corpus.test.ts b/toolkit-docs-generator/tests/scenarios/curation-corpus.test.ts index 17c78e2b6..78c2415f3 100644 --- a/toolkit-docs-generator/tests/scenarios/curation-corpus.test.ts +++ b/toolkit-docs-generator/tests/scenarios/curation-corpus.test.ts @@ -43,7 +43,7 @@ describe("checked-in Markdown curation", () => { subPageCount += current.subPages.length; } - expect(chunkCount).toBe(89); + expect(chunkCount).toBe(93); expect(subPageCount).toBe(2); }); }); From f5cc85af6def483b00c6aed5bc528c69a34c1b46 Mon Sep 17 00:00:00 2001 From: Eric Gustin Date: Fri, 16 Oct 2026 15:44:00 -0700 Subject: [PATCH 3/3] docs(pagerduty): move the integration guide below the tools table and halve it The guide sat between the overview and the tools table, so readers scrolled past about 1,050 words before reaching the tools. Render it in the after_available_tools slot instead, and cut it to about 540 words while keeping every section from PagerDuty's template. --- .../chunks/004-integration-benefits.mdx | 12 +++--- .../pagerduty/chunks/005-how-it-works.mdx | 12 ++---- .../pagerduty/chunks/006-requirements.mdx | 12 +++--- .../curation/pagerduty/chunks/007-support.mdx | 4 +- .../chunks/008-integration-walkthrough.mdx | 39 +++++-------------- .../pagerduty/chunks/009-how-to-uninstall.mdx | 18 ++------- .../data/toolkits/pagerduty.json | 26 ++++++------- 7 files changed, 40 insertions(+), 83 deletions(-) diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/004-integration-benefits.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/004-integration-benefits.mdx index bc0f6f805..72d0b65a7 100644 --- a/toolkit-docs-generator/curation/pagerduty/chunks/004-integration-benefits.mdx +++ b/toolkit-docs-generator/curation/pagerduty/chunks/004-integration-benefits.mdx @@ -1,15 +1,13 @@ --- type: markdown -location: custom_section +location: after_available_tools position: after header: "## PagerDuty + Arcade integration benefits" priority: 10 --- ## PagerDuty + Arcade integration benefits -- **Triage incidents from your AI agent.** List incidents filtered by status, urgency, service, team, or time, read an incident's details and log entries, then acknowledge, resolve, reopen, or reassign it without leaving the agent. -- **Find out who's on call.** Query on-call entries, schedules, and escalation policies to see who's responsible for a service and how PagerDuty escalates its incidents. -- **Look up the people and services involved.** Search users by name or email, and read teams, their members, and services. -- **Use the agent you already have.** The tools work in any MCP client that connects to an Arcade MCP gateway, such as Claude, Cursor, or VS Code, and in agents you build with the Arcade SDKs. -- **Request only the access each tool needs.** Each tool asks for the narrowest PagerDuty OAuth scopes for its job and acts as the PagerDuty user who authorized it. -- **Keep credentials away from the model.** Arcade stores each user's PagerDuty token and calls PagerDuty on the server, so the token never reaches the language model. +- **Triage incidents from your agent:** list, read, acknowledge, resolve, reopen, and reassign incidents. +- **Find out who's on call** from on-call entries, schedules, and escalation policies. +- **Use the agent you already have:** any MCP client connected to an Arcade MCP gateway, such as Claude, Cursor, or VS Code. +- **Least-privilege access:** each tool requests only the scopes it needs and acts as the user who authorized it. Arcade keeps the token away from the language model. diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/005-how-it-works.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/005-how-it-works.mdx index d7ba99cea..c1a821357 100644 --- a/toolkit-docs-generator/curation/pagerduty/chunks/005-how-it-works.mdx +++ b/toolkit-docs-generator/curation/pagerduty/chunks/005-how-it-works.mdx @@ -1,18 +1,12 @@ --- type: markdown -location: custom_section +location: after_available_tools position: after header: "## How it works" priority: 20 --- ## How it works -The Arcade PagerDuty MCP server provides tools that call the [PagerDuty REST API](https://docs.pagerduty.com/developer/api/reference) as the PagerDuty user who authorized them. +The first time a user calls a PagerDuty tool, Arcade returns an authorization link. The user approves Arcade's PagerDuty app on PagerDuty's consent screen, and Arcade stores and refreshes the token from then on. Each tool can only do what its scopes and the user's PagerDuty role allow, and PagerDuty records its actions as that user's. -1. An agent calls a PagerDuty tool through Arcade, for example from an MCP client connected to an Arcade MCP gateway. -2. If the user hasn't authorized PagerDuty yet, Arcade returns an authorization link instead of a result. The user opens the link, signs in to PagerDuty, and approves Arcade's PagerDuty app on PagerDuty's consent screen. -3. Arcade stores the user's token, calls PagerDuty with it, and returns the result to the agent. Later calls reuse the stored authorization. - -Each tool can only do what both its scopes and the user's PagerDuty permissions allow, and PagerDuty records its actions as that user's. Arcade refreshes the token when it expires. Once PagerDuty's refresh window runs out, the next tool call asks the user to authorize again. See PagerDuty's [token lifetimes](https://docs.pagerduty.com/developer/private-apps#token-lifetimes). - -The tools only act when an agent calls them. The integration doesn't send events to PagerDuty, create incidents, or receive webhooks, so it doesn't need a PagerDuty service integration or an integration key. +The tools call the [PagerDuty REST API](https://docs.pagerduty.com/developer/api/reference) only when an agent uses them. The integration doesn't send events, create incidents, or need an integration key. diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/006-requirements.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/006-requirements.mdx index ef88ffd97..30211a900 100644 --- a/toolkit-docs-generator/curation/pagerduty/chunks/006-requirements.mdx +++ b/toolkit-docs-generator/curation/pagerduty/chunks/006-requirements.mdx @@ -1,16 +1,14 @@ --- type: markdown -location: custom_section +location: after_available_tools position: after header: "## Requirements" priority: 30 --- ## Requirements -- **A PagerDuty account with Arcade's PagerDuty app installed.** A PagerDuty administrator installs the app once for the whole account. See the [integration walkthrough](#integration-walkthrough). -- **An Arcade account that's a member of your Arcade project.** Create an Arcade account if you don't have one. -- **An MCP client**, such as Claude, Cursor, or VS Code. You can also try the tools in the Arcade dashboard's Playground without one. +- A PagerDuty account where an administrator has installed Arcade's PagerDuty app. See the [walkthrough](#integration-walkthrough). +- An Arcade account in your Arcade project. Create one if you don't have one. +- An MCP client such as Claude, Cursor, or VS Code, or the Playground in the Arcade dashboard. -Each user authorizes with their own PagerDuty account, so the tools can only do what that user's PagerDuty role allows. - -If you self-host the Arcade Engine, or you're building an agent for people who aren't members of your Arcade project, register your own Scoped OAuth app instead. See the [PagerDuty auth provider](/references/auth-providers/pagerduty). +If you self-host Arcade, or you're building an agent for people outside your Arcade project, register your own Scoped OAuth app with the [PagerDuty auth provider](/references/auth-providers/pagerduty). diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/007-support.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/007-support.mdx index c0423fe4c..4b1657deb 100644 --- a/toolkit-docs-generator/curation/pagerduty/chunks/007-support.mdx +++ b/toolkit-docs-generator/curation/pagerduty/chunks/007-support.mdx @@ -1,14 +1,12 @@ --- type: markdown -location: custom_section +location: after_available_tools position: after header: "## Support" priority: 40 --- ## Support -For help with the Arcade PagerDuty integration: - - Customers on paid plans can email Arcade support at support@arcade.dev. - Anyone can ask in the [Arcade Discord community](https://discord.gg/GUZEMpEZ9p). diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/008-integration-walkthrough.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/008-integration-walkthrough.mdx index eaa75478f..56fb02ab3 100644 --- a/toolkit-docs-generator/curation/pagerduty/chunks/008-integration-walkthrough.mdx +++ b/toolkit-docs-generator/curation/pagerduty/chunks/008-integration-walkthrough.mdx @@ -1,6 +1,6 @@ --- type: markdown -location: custom_section +location: after_available_tools position: after header: "## Integration walkthrough" priority: 50 @@ -9,38 +9,17 @@ priority: 50 ### In PagerDuty -A PagerDuty administrator installs Arcade's PagerDuty app once for the whole account. Until then, nobody in the account can authorize it. +A PagerDuty administrator installs Arcade's app once per account: -1. Sign in to PagerDuty as a user with the Admin or Account Owner role. -2. Go to `https://.pagerduty.com/oauth-apps/PHRMXL1`, where `` is the first part of your PagerDuty web address. -3. Review the app details and the scopes it requests, then click **Install on your account**. +1. Sign in as a user with the Admin or Account Owner role and go to `https://.pagerduty.com/oauth-apps/PHRMXL1`. +2. Review the requested scopes and click **Install on your account**. -If you aren't an administrator, open the same page and click **Copy install link** to send the link to one. - -Installing the app doesn't grant access on its own. Each user authorizes Arcade the first time they use a PagerDuty tool. Arcade doesn't use PagerDuty's Events API, so you don't need to add an integration to a service or copy an integration key. +If you aren't an administrator, click **Copy install link** on that page and send the link to one. You don't need a service integration or an integration key. ### In Arcade -**1. Create an MCP gateway with the PagerDuty tools** - -1. Sign in to the [Arcade dashboard](https://app.arcade.dev) and select **MCP gateways**. -2. Click **Create MCP gateway**. -3. Under **Name it**, enter a name such as `PagerDuty`. -4. Under **Select apps**, find **PagerDuty** and select it to add all of its tools. -5. Under **Choose who connects**, select **Members of this Project**. -6. Click **Create MCP gateway**. - -For the other gateway options, see [Create via Dashboard](/operate/governance/mcp-gateways/create-via-dashboard). - -**2. Connect your MCP client** - -In the **MCP gateways** list, open the gateway's actions menu, select **Connect to client**, and follow the steps for your client. [Connect to MCP Clients](/get-started/mcp-clients) has a guide for each supported client. - -**3. Authorize PagerDuty** - -1. Ask your agent a PagerDuty question, such as "Which PagerDuty incidents are open right now?" -2. The first PagerDuty tool call returns an authorization link. Open it, and sign in to Arcade if prompted. -3. Sign in to PagerDuty, review the requested scopes, and click **Submit Consent**. -4. Return to your agent. If it doesn't continue on its own, ask again. +1. In the [Arcade dashboard](https://app.arcade.dev), go to **MCP gateways** and click **Create MCP gateway**. Under **Select apps**, select **PagerDuty**. Under **Choose who connects**, select **Members of this Project**. Then create the gateway. For the other options, see [Create via Dashboard](/operate/governance/mcp-gateways/create-via-dashboard). +2. Open the gateway's actions menu, select **Connect to client**, and follow the steps for your MCP client. +3. Ask your agent a PagerDuty question, such as "Which incidents are open right now?" Open the authorization link it returns, sign in to PagerDuty, and click **Submit Consent**. -To try the tools without an MCP client, open **Playground** in the Arcade dashboard, click **Select Tools**, add the PagerDuty tools, and ask the same question. +To try the tools without an MCP client, open the Playground in the Arcade dashboard, click **Select Tools**, and add PagerDuty. diff --git a/toolkit-docs-generator/curation/pagerduty/chunks/009-how-to-uninstall.mdx b/toolkit-docs-generator/curation/pagerduty/chunks/009-how-to-uninstall.mdx index ba27e3412..d1c38afe6 100644 --- a/toolkit-docs-generator/curation/pagerduty/chunks/009-how-to-uninstall.mdx +++ b/toolkit-docs-generator/curation/pagerduty/chunks/009-how-to-uninstall.mdx @@ -1,23 +1,13 @@ --- type: markdown -location: custom_section +location: after_available_tools position: after header: "## How to uninstall" priority: 60 --- ## How to uninstall -Remove the integration in both Arcade and PagerDuty. Revoking a connection in Arcade deletes the token Arcade stores, but it doesn't revoke the authorization in PagerDuty. +Revoking in Arcade deletes the stored token but leaves the authorization in PagerDuty, so do both: -### In Arcade - -- **Remove the tools from your gateway.** In **MCP gateways**, open the gateway's actions menu and select **Edit gateway**. Under **Select apps**, clear **PagerDuty**, then click **Save changes**. To remove the whole gateway, select **Delete gateway** instead. -- **Delete stored authorizations.** Go to **Connections** > **Connected users**, filter the list to the PagerDuty provider, and click **Revoke** on each connection. Revoking requires the Admin or Member project role. - -### In PagerDuty - -Go to **Integrations** > **OAuth Apps** and select **Arcade.dev**. Then: - -- **To revoke your own access**, click **Revoke Your User Token**. -- **To revoke every user's access** (administrators only), click **Revoke All User Tokens**. Each user must authorize again to keep using the tools. -- **To remove the app from your account** (administrators only), click **Uninstall**. This revokes every user's token, and nobody can authorize the app again until an administrator reinstalls it. +- **In Arcade:** edit the gateway and clear **PagerDuty** under **Select apps**, or delete the gateway. Then revoke the PagerDuty connections under **Connections** > **Connected users**. +- **In PagerDuty:** go to **Integrations** > **OAuth Apps** > **Arcade.dev** and click **Revoke Your User Token**. Administrators can click **Revoke All User Tokens** instead, or **Uninstall** to remove the app from the account. diff --git a/toolkit-docs-generator/data/toolkits/pagerduty.json b/toolkit-docs-generator/data/toolkits/pagerduty.json index 6dbdcd469..5ed2a7ef9 100644 --- a/toolkit-docs-generator/data/toolkits/pagerduty.json +++ b/toolkit-docs-generator/data/toolkits/pagerduty.json @@ -1432,56 +1432,56 @@ }, { "type": "markdown", - "location": "custom_section", + "location": "after_available_tools", "position": "after", - "content": "## PagerDuty + Arcade integration benefits\n\n- **Triage incidents from your AI agent.** List incidents filtered by status, urgency, service, team, or time, read an incident's details and log entries, then acknowledge, resolve, reopen, or reassign it without leaving the agent.\n- **Find out who's on call.** Query on-call entries, schedules, and escalation policies to see who's responsible for a service and how PagerDuty escalates its incidents.\n- **Look up the people and services involved.** Search users by name or email, and read teams, their members, and services.\n- **Use the agent you already have.** The tools work in any MCP client that connects to an Arcade MCP gateway, such as Claude, Cursor, or VS Code, and in agents you build with the Arcade SDKs.\n- **Request only the access each tool needs.** Each tool asks for the narrowest PagerDuty OAuth scopes for its job and acts as the PagerDuty user who authorized it.\n- **Keep credentials away from the model.** Arcade stores each user's PagerDuty token and calls PagerDuty on the server, so the token never reaches the language model.", + "content": "## PagerDuty + Arcade integration benefits\n\n- **Triage incidents from your agent:** list, read, acknowledge, resolve, reopen, and reassign incidents.\n- **Find out who's on call** from on-call entries, schedules, and escalation policies.\n- **Use the agent you already have:** any MCP client connected to an Arcade MCP gateway, such as Claude, Cursor, or VS Code.\n- **Least-privilege access:** each tool requests only the scopes it needs and acts as the user who authorized it. Arcade keeps the token away from the language model.", "header": "## PagerDuty + Arcade integration benefits", "priority": 10 }, { "type": "markdown", - "location": "custom_section", + "location": "after_available_tools", "position": "after", - "content": "## How it works\n\nThe Arcade PagerDuty MCP server provides tools that call the [PagerDuty REST API](https://docs.pagerduty.com/developer/api/reference) as the PagerDuty user who authorized them.\n\n1. An agent calls a PagerDuty tool through Arcade, for example from an MCP client connected to an Arcade MCP gateway.\n2. If the user hasn't authorized PagerDuty yet, Arcade returns an authorization link instead of a result. The user opens the link, signs in to PagerDuty, and approves Arcade's PagerDuty app on PagerDuty's consent screen.\n3. Arcade stores the user's token, calls PagerDuty with it, and returns the result to the agent. Later calls reuse the stored authorization.\n\nEach tool can only do what both its scopes and the user's PagerDuty permissions allow, and PagerDuty records its actions as that user's. Arcade refreshes the token when it expires. Once PagerDuty's refresh window runs out, the next tool call asks the user to authorize again. See PagerDuty's [token lifetimes](https://docs.pagerduty.com/developer/private-apps#token-lifetimes).\n\nThe tools only act when an agent calls them. The integration doesn't send events to PagerDuty, create incidents, or receive webhooks, so it doesn't need a PagerDuty service integration or an integration key.", + "content": "## How it works\n\nThe first time a user calls a PagerDuty tool, Arcade returns an authorization link. The user approves Arcade's PagerDuty app on PagerDuty's consent screen, and Arcade stores and refreshes the token from then on. Each tool can only do what its scopes and the user's PagerDuty role allow, and PagerDuty records its actions as that user's.\n\nThe tools call the [PagerDuty REST API](https://docs.pagerduty.com/developer/api/reference) only when an agent uses them. The integration doesn't send events, create incidents, or need an integration key.", "header": "## How it works", "priority": 20 }, { "type": "markdown", - "location": "custom_section", + "location": "after_available_tools", "position": "after", - "content": "## Requirements\n\n- **A PagerDuty account with Arcade's PagerDuty app installed.** A PagerDuty administrator installs the app once for the whole account. See the [integration walkthrough](#integration-walkthrough).\n- **An Arcade account that's a member of your Arcade project.** Create an Arcade account if you don't have one.\n- **An MCP client**, such as Claude, Cursor, or VS Code. You can also try the tools in the Arcade dashboard's Playground without one.\n\nEach user authorizes with their own PagerDuty account, so the tools can only do what that user's PagerDuty role allows.\n\nIf you self-host the Arcade Engine, or you're building an agent for people who aren't members of your Arcade project, register your own Scoped OAuth app instead. See the [PagerDuty auth provider](/references/auth-providers/pagerduty).", + "content": "## Requirements\n\n- A PagerDuty account where an administrator has installed Arcade's PagerDuty app. See the [walkthrough](#integration-walkthrough).\n- An Arcade account in your Arcade project. Create one if you don't have one.\n- An MCP client such as Claude, Cursor, or VS Code, or the Playground in the Arcade dashboard.\n\nIf you self-host Arcade, or you're building an agent for people outside your Arcade project, register your own Scoped OAuth app with the [PagerDuty auth provider](/references/auth-providers/pagerduty).", "header": "## Requirements", "priority": 30 }, { "type": "markdown", - "location": "custom_section", + "location": "after_available_tools", "position": "after", - "content": "## Support\n\nFor help with the Arcade PagerDuty integration:\n\n- Customers on paid plans can email Arcade support at support@arcade.dev.\n- Anyone can ask in the [Arcade Discord community](https://discord.gg/GUZEMpEZ9p).\n\nThe [Arcade contact page](/resources/contact-us) lists every support channel.", + "content": "## Support\n\n- Customers on paid plans can email Arcade support at support@arcade.dev.\n- Anyone can ask in the [Arcade Discord community](https://discord.gg/GUZEMpEZ9p).\n\nThe [Arcade contact page](/resources/contact-us) lists every support channel.", "header": "## Support", "priority": 40 }, { "type": "markdown", - "location": "custom_section", + "location": "after_available_tools", "position": "after", - "content": "## Integration walkthrough\n\n### In PagerDuty\n\nA PagerDuty administrator installs Arcade's PagerDuty app once for the whole account. Until then, nobody in the account can authorize it.\n\n1. Sign in to PagerDuty as a user with the Admin or Account Owner role.\n2. Go to `https://.pagerduty.com/oauth-apps/PHRMXL1`, where `` is the first part of your PagerDuty web address.\n3. Review the app details and the scopes it requests, then click **Install on your account**.\n\nIf you aren't an administrator, open the same page and click **Copy install link** to send the link to one.\n\nInstalling the app doesn't grant access on its own. Each user authorizes Arcade the first time they use a PagerDuty tool. Arcade doesn't use PagerDuty's Events API, so you don't need to add an integration to a service or copy an integration key.\n\n### In Arcade\n\n**1. Create an MCP gateway with the PagerDuty tools**\n\n1. Sign in to the [Arcade dashboard](https://app.arcade.dev) and select **MCP gateways**.\n2. Click **Create MCP gateway**.\n3. Under **Name it**, enter a name such as `PagerDuty`.\n4. Under **Select apps**, find **PagerDuty** and select it to add all of its tools.\n5. Under **Choose who connects**, select **Members of this Project**.\n6. Click **Create MCP gateway**.\n\nFor the other gateway options, see [Create via Dashboard](/operate/governance/mcp-gateways/create-via-dashboard).\n\n**2. Connect your MCP client**\n\nIn the **MCP gateways** list, open the gateway's actions menu, select **Connect to client**, and follow the steps for your client. [Connect to MCP Clients](/get-started/mcp-clients) has a guide for each supported client.\n\n**3. Authorize PagerDuty**\n\n1. Ask your agent a PagerDuty question, such as \"Which PagerDuty incidents are open right now?\"\n2. The first PagerDuty tool call returns an authorization link. Open it, and sign in to Arcade if prompted.\n3. Sign in to PagerDuty, review the requested scopes, and click **Submit Consent**.\n4. Return to your agent. If it doesn't continue on its own, ask again.\n\nTo try the tools without an MCP client, open **Playground** in the Arcade dashboard, click **Select Tools**, add the PagerDuty tools, and ask the same question.", + "content": "## Integration walkthrough\n\n### In PagerDuty\n\nA PagerDuty administrator installs Arcade's app once per account:\n\n1. Sign in as a user with the Admin or Account Owner role and go to `https://.pagerduty.com/oauth-apps/PHRMXL1`.\n2. Review the requested scopes and click **Install on your account**.\n\nIf you aren't an administrator, click **Copy install link** on that page and send the link to one. You don't need a service integration or an integration key.\n\n### In Arcade\n\n1. In the [Arcade dashboard](https://app.arcade.dev), go to **MCP gateways** and click **Create MCP gateway**. Under **Select apps**, select **PagerDuty**. Under **Choose who connects**, select **Members of this Project**. Then create the gateway. For the other options, see [Create via Dashboard](/operate/governance/mcp-gateways/create-via-dashboard).\n2. Open the gateway's actions menu, select **Connect to client**, and follow the steps for your MCP client.\n3. Ask your agent a PagerDuty question, such as \"Which incidents are open right now?\" Open the authorization link it returns, sign in to PagerDuty, and click **Submit Consent**.\n\nTo try the tools without an MCP client, open the Playground in the Arcade dashboard, click **Select Tools**, and add PagerDuty.", "header": "## Integration walkthrough", "priority": 50 }, { "type": "markdown", - "location": "custom_section", + "location": "after_available_tools", "position": "after", - "content": "## How to uninstall\n\nRemove the integration in both Arcade and PagerDuty. Revoking a connection in Arcade deletes the token Arcade stores, but it doesn't revoke the authorization in PagerDuty.\n\n### In Arcade\n\n- **Remove the tools from your gateway.** In **MCP gateways**, open the gateway's actions menu and select **Edit gateway**. Under **Select apps**, clear **PagerDuty**, then click **Save changes**. To remove the whole gateway, select **Delete gateway** instead.\n- **Delete stored authorizations.** Go to **Connections** > **Connected users**, filter the list to the PagerDuty provider, and click **Revoke** on each connection. Revoking requires the Admin or Member project role.\n\n### In PagerDuty\n\nGo to **Integrations** > **OAuth Apps** and select **Arcade.dev**. Then:\n\n- **To revoke your own access**, click **Revoke Your User Token**.\n- **To revoke every user's access** (administrators only), click **Revoke All User Tokens**. Each user must authorize again to keep using the tools.\n- **To remove the app from your account** (administrators only), click **Uninstall**. This revokes every user's token, and nobody can authorize the app again until an administrator reinstalls it.", + "content": "## How to uninstall\n\nRevoking in Arcade deletes the stored token but leaves the authorization in PagerDuty, so do both:\n\n- **In Arcade:** edit the gateway and clear **PagerDuty** under **Select apps**, or delete the gateway. Then revoke the PagerDuty connections under **Connections** > **Connected users**.\n- **In PagerDuty:** go to **Integrations** > **OAuth Apps** > **Arcade.dev** and click **Revoke Your User Token**. Administrators can click **Revoke All User Tokens** instead, or **Uninstall** to remove the app from the account.", "header": "## How to uninstall", "priority": 60 } ], "customImports": [], "subPages": [], - "curationSourceHash": "1a945a964740f4fc063301803f29511728f9b3b18be934cc0978ce382d9d6e00", + "curationSourceHash": "a976f2f9feb1945c67a781a990b555a303121632269fcf100db4df8e358ac216", "generatedAt": "2026-10-07T21:25:50.988Z", "summary": "## PagerDuty Toolkit\n\nThe Arcade PagerDuty toolkit lets LLMs interact with PagerDuty to query and manage incidents, on-call schedules, teams, services, and escalation policies.\n\n## Capabilities\n\n- **Incident management** — retrieve, list (with filters for status, urgency, service, team, and time), update status (acknowledge, resolve, reopen), and reassign incidents to specific users.\n- **On-call & scheduling** — list on-call entries, schedules, and escalation policies; fetch individual policies by ID.\n- **Teams, users & services** — list and look up teams (with members and linked resources), users, and services; fuzzy-search users by name or email; retrieve individual records by ID.\n- **Activity feed** — list log entries showing incident triggers, acknowledgments, escalations, and resolutions across the account.\n- **Identity** — retrieve the authenticated user's PagerDuty profile including contact and notification summaries via `Whoami`.\n\n## OAuth\n\nThis toolkit uses OAuth 2.0 via the **PagerDuty** Arcade auth provider. See the [PagerDuty provider docs](https://docs.arcade.dev/en/references/auth-providers/pagerduty) for configuration details." } \ No newline at end of file