pagerduty-mcp
Enables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.
README
pagerduty-mcp
Dedalus MCP server for PagerDuty incident response. It exposes incident reads, incident acknowledgement and resolution, on-call lookup, and service listing.
Tools
list_incidents- List incidents with status, service, and time filters.get_incident- Fetch one incident by ID.acknowledge_incident- Acknowledge an incident.resolve_incident- Resolve an incident.list_oncalls- List on-call entries.list_services- List PagerDuty services.
Safety Notes
acknowledge_incident and resolve_incident are high-impact incident-response writes. Acknowledging may change escalation behavior. Resolving may stop paging and incident follow-up. Require explicit user intent and a specific incident ID before calling either tool.
PagerDuty writes require a From email for auditability. Pass from_email or set PAGERDUTY_FROM_EMAIL.
Never commit API tokens, incident exports, escalation policy data, or user schedules.
Authentication
This implementation targets Dedalus Type 3 DAuth API-token auth. It declares a connection named pagerduty-mcp with secret key PAGERDUTY_API_TOKEN and sends Authorization: Token token=<token> through the DAuth dispatch layer.
Environment variables:
PAGERDUTY_API_TOKEN=...
PAGERDUTY_FROM_EMAIL=oncall-admin@example.com
DEDALUS_AS_URL=https://as.dedaluslabs.ai
If your PagerDuty OAuth app is ready, configure OAuth variables in Dedalus and keep the same bearer-compatible connection model only after verifying the token header expected by your app.
Run Locally
uv run python src/main.py
In another terminal:
MCP_SERVER_URL=http://127.0.0.1:8080/mcp uv run python src/_client.py
Set PAGERDUTY_TEST_INCIDENT_ID to a safe test incident. The client intentionally calls the write tools, so do not point it at a production incident unless that is the intended test.
Deploy
Publish as dedalus-labs/pagerduty-mcp, configure PAGERDUTY_API_TOKEN as a required DAuth credential, deploy, then run:
DEDALUS_MCP_SERVER_ONLY=1 DEDALUS_MCP_SERVER=dedalus-labs/pagerduty-mcp uv run python src/_client.py
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.