Build a PagerDuty incident dashboard with Claude

This is an end-to-end example: connect a data source over MCP, generate a dashboard from live numbers, and close the review loop on one link. Total time, start to shared link, is under fifteen minutes. The same shape works for any of the other examples — only the connection step changes.

Here's the finished dashboard, published to a canvas — click any tile or number to leave a comment, exactly as your team would:

The three moving parts

1. The PagerDuty MCP server gives Claude read access to your PagerDuty account — incidents, services, schedules, escalation policies, on-calls — through a controlled set of tools. You approve what it can touch.
2. Claude pulls the numbers and writes a single self-contained HTML dashboard. You iterate on it in the artifact panel until it's right.
3. Drafty turns that HTML into a stable link your team reviews. Comments pin to the exact element; Claude ships the fix to the same URL.

The generation step is fast now. The part this example is really about is the third one — getting the dashboard in front of people without losing their feedback to a screenshot circled in Preview.

Step 1 — Connect the PagerDuty MCP server

PagerDuty runs an official remote MCP server at https://mcp.pagerduty.com/mcp. You connect once; it authenticates over OAuth, so no token is pasted into a config file. (EU accounts use https://mcp.eu.pagerduty.com/mcp.)

In Claude Code:

Then run /mcp inside Claude Code and follow the OAuth prompt to authorize the account. The remote server is read-only out of the box — write tools are opt-in — which is exactly what a reporting dashboard needs.

In Claude Desktop: open Settings → Connectors → Add custom connector, paste https://mcp.pagerduty.com/mcp, and authorize with OAuth the same way.

Step 2 — Pull the numbers

Ask Claude in plain language. It uses the MCP server's read tools to fetch real incident data:

Claude calls PagerDuty, returns the figures, and you sanity-check them against the PagerDuty Analytics view before going further. This is the moment to catch a wrong assumption — a time window off by a day, low-urgency noise inflating the count, a service you forgot to scope out — while it's cheap.

Step 3 — Build the dashboard

Once the numbers look right, ask for the artifact:

Claude renders it live in the artifact panel. Iterate in place — you're not regenerating from scratch:

• "Make MTTR the biggest number and put MTTA right under it."
• "Add a 6-week MTTR trend line so we can see if it's improving."
• "Sort the by-service chart descending and only show the top 6."

Step 4 — Publish to Drafty for review

A Claude artifact link is a preview, not a stable URL — iterate the artifact and the link you already sent now shows the old version. Ask Claude to publish it to a Drafty canvas instead, so the link you share always stays current:

Claude pushes the dashboard and hands back a drafty.im/canvas/… link that renders on any device. Send it — your team opens it in a browser, no login and no Claude account needed.

Step 5 — The review loop

This is the part that's not obvious until you've done it once.

A reviewer clicks the specific tile, chart, or number they want changed and leaves a pinned comment — "this MTTR looks low, are we excluding the incidents that auto-resolved?" The comment is anchored to that element, not floating in a Slack thread. Claude reads the comments through the CLI, reruns the relevant PagerDuty query if needed, and pushes a revised dashboard to the same URL. The reviewer refreshes and sees the change; the thread stays attached to the element.

The mechanic matters because of what it removes. A Slack message about a chart produces "the number on the left looks wrong." A pinned comment on the actual tile produces "this — exclude auto-resolved incidents from the MTTR." One of those produces a correct revision; the other produces a guess.

Keeping it fresh

An MCP-generated dashboard is a snapshot — it holds the numbers Claude pulled when it built it; it doesn't re-query PagerDuty when someone opens the link. For a weekly reliability review or an incident retro, that's fine.

To make it a live canvas that always shows today's figures, copy this prompt — Claude sets up the refresh for you and schedules it to run on its own:

The link stays stable while the content updates underneath it — see keeping a canvas updated automatically.

What to watch for

• Read-only, always. A reliability dashboard needs read access and nothing more. Stay in the remote server's default read-only mode, or scope a User API token to read access — never enable write tools.
• Check the figures before you share. The MCP returns exactly what you ask for — if your MTTR query includes low-urgency noise or counts incidents the wrong window, the dashboard will confidently show the wrong number. Reconcile against the PagerDuty Analytics view once.
• The link is the deliverable, not the artifact. Share the Drafty URL, not the Claude artifact preview — that's the one you can update in place.