M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionPagerDuty MCP ServerPagerDuty's official MCP server for managing incidents and on-call from your IDE or chat clientContext7Upstash's official server providing up-to-date third-party library docs for AI coding assistants
FMRS64 / 100 · C80 / 100 · B
Reliability8 / 2014 / 20
Security and permissions14 / 2016 / 20
Maintenance11 / 2017 / 20
Documentation17 / 2015 / 20
Setup experience14 / 2018 / 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
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)
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
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
Supported clientsClaude Desktop, Cursor, VS CodeClaude Code, VS Code, Cursor, Cline, Amp
Tools822