Can I acknowledge and resolve incidents directly from my AI agent?

Yes! Use the `update_incident` tool with the incident ID and your PagerDuty email. Set status to `acknowledged` or `resolved` to change the incident state instantly without opening the PagerDuty dashboard.

How do I find out who is on-call right now?

Run the `list_oncalls` tool. It returns every user currently on-call across all schedules and escalation levels, showing their name, escalation policy, and coverage window.

Can I create incidents programmatically for testing or escalation?

Absolutely. Use `create_incident` with your PagerDuty email, the target service ID, a descriptive title, and optionally set urgency to `high` or `low`. The incident will immediately trigger according to the service's escalation policy.

PagerDuty MCP Server for VS Code Copilot 11 tools — connect in under 2 minutes

Name: PagerDuty
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 11 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install PagerDuty and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "pagerduty": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About PagerDuty MCP Server

Connect your PagerDuty account to any AI agent and take full control of incident management operations through natural conversation.

GitHub Copilot Agent mode brings PagerDuty data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Incident Management — List, create, acknowledge, and resolve incidents across all services
Service Monitoring — Browse all monitored services and inspect their configurations, integrations, and health status
User Management — List all team members, view individual profiles, contact methods, and notification rules
On-Call Visibility — See who is currently on-call across all schedules and escalation levels in real-time
Schedule Administration — Browse rotation schedules with their layers, handoff times, and coverage windows
Escalation Policies — Inspect escalation chains to understand how incidents route through teams

The PagerDuty MCP Server exposes 11 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect PagerDuty to VS Code Copilot via MCP

Follow these steps to integrate the PagerDuty MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using PagerDuty

Ask Copilot: "Using PagerDuty, help me...". 11 tools available

Why Use VS Code Copilot with the PagerDuty MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with PagerDuty through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

PagerDuty + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the PagerDuty MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

PagerDuty MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect PagerDuty to VS Code Copilot via MCP:

create_incident

Requires the From header email (your PagerDuty user email), service ID, and incident title. Create a new incident on a service

get_incident

Get detailed information about a specific incident

get_service

Get detailed configuration of a specific service

get_user

Get detailed information about a specific user

list_escalation_policies

List all escalation policies

list_incidents

Optionally filter by status: triggered, acknowledged, resolved. List incidents across all services

list_oncalls

List who is currently on-call across all schedules

list_schedules

List all on-call schedules

list_services

List all monitored services

list_users

List all users in the PagerDuty account

update_incident

Use to acknowledge, resolve, or reassign incidents programatically. Update an incident status (acknowledge, resolve, escalate)

Example Prompts for PagerDuty in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with PagerDuty immediately.

"Show me all triggered incidents right now."

"Who is on-call for the Platform team right now?"

"Acknowledge incident P8K2LMN and show me the service details."

Troubleshooting PagerDuty MCP Server with VS Code Copilot

Common issues when connecting PagerDuty to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

PagerDuty + VS Code Copilot FAQ

Common questions about integrating PagerDuty MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.