pagerduty-mcp-server vs RunLater
pagerduty-mcp-server is an MCP server published by wpfleger96. Marketplaces we read that list it: 1 (PyPI (MCP servers)). RunLater is an MCP server published by runlater.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  pagerduty-mcp-server | |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 4.1.0 Downloads/month (PyPI): 608 Downloads/week (PyPI): 514 Forks (GitHub): 13 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | pagerduty-mcp-server | RunLater |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 8 | No figure on GitHub |
| Forks (GitHub) (differs) | 13 | No figure on GitHub |
| Last release (differs) | 2026-11-10 (better) | 2026-11-06 (worse) |
| Where it runs (differs) | On your machine (pagerduty-mcp-server) | Remote server (runlater.app/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/wpfleger96/pagerduty-mcp-server | Not stated |
| Changes in the last 7 days (differs) | 1 | 3 |
| First seen (differs) | 2026-10-13 | 2026-11-05 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 22 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
pagerduty-mcp-server
MCP server for LLM agents to interact with PagerDuty SaaS
RunLater
Schedule HTTP requests from an agent: once at an exact time or on cron, with retries and run logs.
How to run each
pagerduty-mcp-server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
RunLater As a remote MCP server
claude mcp add --transport http runlater https://runlater.app/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only RunLater has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: pagerduty-mcp-server · What it can do: RunLater · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.