com.mcparmory/datadog vs DevHelm MCP Server
com.mcparmory/datadog is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). DevHelm MCP Server is an MCP server published by devhelmhq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  com.mcparmory/datadog |  DevHelm MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (PyPI): 812 Downloads/week (PyPI): 180 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 1.0.2 Downloads/month (PyPI): 128 Downloads/week (PyPI): 120 Forks (GitHub): 0 Stars (GitHub): 1 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 | com.mcparmory/datadog | DevHelm MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 32 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcparmory-datadog) | On your machine (devhelm-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mcparmory/registry | github.com/devhelmhq/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
com.mcparmory/datadog
Monitor infrastructure, manage agents and deployments, track metrics, logs, and events
DevHelm MCP Server
Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm
How to run each
com.mcparmory/datadog As a local MCP server: PyPI package
claude mcp add --transport stdio datadog -- uvx mcparmory-datadogDevHelm MCP Server As a local MCP server: PyPI package
claude mcp add --env "DEVHELM_API_TOKEN=<YOUR_DEVHELM_API_TOKEN>" --transport stdio devhelm-mcp-server -- uvx devhelm-mcp-serverRequires: DEVHELM_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of com.mcparmory/datadog publish no settings it asks for, so we do not compare settings.
What it can do: com.mcparmory/datadog · What it can do: DevHelm MCP Server · Compare two other plugins
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.