Amazon CloudWatch Application Signals vs harness-mcp-v2
Amazon CloudWatch Application Signals is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). harness-mcp-v2 is an MCP server published by harness. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |  Amazon CloudWatch Application Signals |  harness-mcp-v2 |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:873bf1023b30 Forks (GitHub): 1 867 Pulls (Docker Hub): 14 584 Stars (Docker Hub): 1 Stars (GitHub): 9 899 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 3.2.40 Downloads/month (npm): 18 285 Downloads/week (npm): 9 274 Forks (GitHub): 97 Stars (GitHub): 113 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 | Amazon CloudWatch Application Signals | harness-mcp-v2 |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 899 (better) | 113 (worse) |
| Pulls (Docker Hub) (differs) | 14 584 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 867 (better) | 97 (worse) |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | On your machine (mcp/cloudwatch-appsignals-mcp-server) | On your machine (harness-mcp-v2) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/harness/mcp-server |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
Amazon CloudWatch Application Signals
Application performance monitoring and insights.
harness-mcp-v2
Give AI agents full access to the Harness.io platform — manage pipelines, deployments, cloud costs, chaos engineering, feature flags, SEI, and 125+ resource types through 11 MCP tools
How to run each
Amazon CloudWatch Application Signals As a local MCP server: Docker image
claude mcp add --transport stdio awslabs-cloudwatch-appsignals -- docker run -i --rm mcp/cloudwatch-appsignals-mcp-serverharness-mcp-v2
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of harness-mcp-v2 publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of harness-mcp-v2 publish no settings it asks for, so we do not compare settings.
What it can do: Amazon CloudWatch Application Signals · What it can do: harness-mcp-v2 · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.