| FMRS | 64 / 100 · C | 80 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 8 / 20 | 14 / 20 | 13 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 | 14 / 20 |
|---|
| Maintenance | 11 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 17 / 20 | 15 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 18 / 20 | 14 / 20 |
|---|
| Best for | - SREs / on-call engineers already using PagerDuty
- DevOps teams wanting AI-assisted incident triage without leaving their IDE
- Teams that want to query incident metrics or manage schedules conversationally
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Teams that don't use PagerDuty
- Organizations requiring strict least-privilege, role-scoped tokens (this server uses a user-level API token with that user's full account privileges)
- Deployments that expose the HTTP endpoint directly on untrusted networks without an authenticating reverse proxy
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Requires a PagerDuty User API Token (`PAGERDUTY_USER_API_KEY`) with that user's full privileges on the PagerDuty account
- Only read-only tools are exposed by default; `--enable-write-tools` must be explicitly set to create, update, or delete incidents, services, teams, schedules, escalation policies, webhooks, and status page content
- Optional `PAGERDUTY_API_HOST` to target the standard or EU regional API endpoint
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - The streamable-http and sse transports have no built-in authentication — any client able to reach the host/port can invoke tools, including write tools, using the single API key the server was started with; the README explicitly warns to keep the default loopback bind and only expose 0.0.0.0 behind an authenticating reverse proxy/gateway
- Write tools are powerful: they can delete teams, modify escalation policies and schedules, and create status page incident posts, so mistakes can disrupt real on-call routing or customer-visible status pages
- Creating a webhook subscription returns a signing secret that must be stored securely
- Claude Desktop's config file requires the API key to be stored in plaintext, so file permissions matter
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Desktop, Cursor, VS Code | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Amp |
|---|
| Tools | 82 | 2 | 15 |
|---|