Amazon CloudWatch Application Signals vs io.github.lhf552004/cloudpulse
Amazon CloudWatch Application Signals is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.lhf552004/cloudpulse is an MCP server published by lhf552004. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  io.github.lhf552004/cloudpulse |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:873bf1023b30 Forks (GitHub): 1 826 Pulls (Docker Hub): 14 222 Stars (Docker Hub): 1 Stars (GitHub): 9 823 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Downloads/month (npm): 167 Downloads/week (npm): 19 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 | Amazon CloudWatch Application Signals | io.github.lhf552004/cloudpulse |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 823 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 14 222 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 826 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/cloudwatch-appsignals-mcp-server) | On your machine (cloudpulse-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 8, secrets among them: 4 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/galadriel-tech-solutions/cloudpulse-mcp |
| 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
Amazon CloudWatch Application Signals
Application performance monitoring and insights.
io.github.lhf552004/cloudpulse
Cross-cloud observability for AI agents. Covers AWS, GCP, Vercel, and Cloudflare.
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-serverio.github.lhf552004/cloudpulse As a local MCP server: npm package
claude mcp add --env "AWS_ACCESS_KEY_ID=<YOUR_AWS_ACCESS_KEY_ID>" --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "CLOUDFLARE_API_TOKEN=<YOUR_CLOUDFLARE_API_TOKEN>" --env "VERCEL_TOKEN=<YOUR_VERCEL_TOKEN>" --transport stdio cloudpulse -- npx -y cloudpulse-mcpRequires: AWS_ACCESS_KEY_ID (secret), AWS_SECRET_ACCESS_KEY (secret), CLOUDFLARE_API_TOKEN (secret), VERCEL_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.lhf552004/cloudpulse publish no list of tools, so we do not compare tools.
Settings each asks for
Only Amazon CloudWatch Application Signals asks for
AWS_PROFILE
Only io.github.lhf552004/cloudpulse asks for
AWS_ACCESS_KEY_ID (secret)AWS_SECRET_ACCESS_KEY (secret)CLOUDFLARE_ACCOUNT_IDCLOUDFLARE_API_TOKEN (secret)GOOGLE_APPLICATION_CREDENTIALSGOOGLE_CLOUD_PROJECTVERCEL_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Amazon CloudWatch Application Signals · What it can do: io.github.lhf552004/cloudpulse · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.