MCP PagerDuty

🚧 Early Development - Work in Progress 🚧

A Model Context Protocol (MCP) server that provides integration with PagerDuty for incident management and monitoring operations.

⚠️ Project Status

This project is in its initial development phase. Many features are planned but not yet implemented. Contributions and feedback are welcome!

🚀 Getting Started

Prerequisites

• Python 3.13 or higher
• PagerDuty API token

Installation

1. Clone the repository

git clone https://github.com/judexzhu/mcp-pagerduty.git
   cd mcp-pagerduty

2. Install dependencies with UV

uv sync

3. Configure environment

cp .env.example .env
   # Edit .env with your PagerDuty API credentials

Configuration

Create a .env file with your PagerDuty configuration:

PAGERDUTY_API_TOKEN=your_api_token_here
PAGERDUTY_API_URL=https://api.pagerduty.com

Note: PAGERDUTY_API_URL is optional and defaults to https://api.pagerduty.com if not specified.

🔧 Development

This project is actively under development. Current structure:

mcp-pagerduty/
├── pagerduty.py          # Main MCP server implementation
├── pyproject.toml        # Project configuration
├── .env                  # Environment variables (create from .env.example)
└── README.md            # This file

Running the Server

python pagerduty.py

📚 MCP Integration

This server implements the Model Context Protocol to provide PagerDuty functionality to AI assistants and other MCP clients.

Current Tools

• pagerduty_list_incidents - List incidents with filtering options
• pagerduty_get_incident - Get detailed incident information
• pagerduty_get_incident_notes - Get detailed incident information

Planned Resources

• Incident templates
• Escalation policy information
• Service status dashboards

🤝 Contributing

This project is in early development and contributions are very welcome!

How to Contribute

1. Fork the repository

2. Create a feature branch

git checkout -b feature/your-feature-name

3. Make your changes

4. Add tests (when testing framework is set up)

5. Submit a pull request

Development Priorities

Current development priorities:

1. 🔴 High Priority: Basic incident listing and retrieval

2. 🟡 Medium Priority: Incident creation and updates

3. 🟢 Low Priority: Advanced features like escalation management

📋 TODO

• [ ] Implement basic MCP server structure
• [ ] Add PagerDuty API client
• [ ] Implement incident management tools
• [ ] Add comprehensive error handling
• [ ] Write tests
• [ ] Add logging and monitoring
• [ ] Create example configurations
• [ ] Write comprehensive documentation

🐛 Known Issues

• Project is in initial development phase
• No functionality implemented yet
• API integration not yet built

📖 Resources

• PagerDuty API Documentation
• Model Context Protocol Specification
• MCP Python SDK

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🆘 Support

Since this project is in early development:

• 📝 Documentation: Coming soon
• 🐛 Bug Reports: Please open an issue
• 💡 Feature Requests: Welcome via issues
• 💬 Questions: Open a discussion or issue

---

Note: This project is not affiliated with PagerDuty, Inc. It's a community-driven integration for the Model Context Protocol.