Amazon CloudWatch Application Signals vs io.github.alexpota/cloudscope
Amazon CloudWatch Application Signals is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.alexpota/cloudscope is an MCP server published by alexpota. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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.alexpota/cloudscope |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:873bf1023b30 Forks (GitHub): 1 815 Pulls (Docker Hub): 14 015 Stars (Docker Hub): 1 Stars (GitHub): 9 788 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.3 Downloads/month (npm): 255 Downloads/week (npm): 50 Forks (GitHub): 1 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.alexpota/cloudscope |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 788 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 14 015 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 815 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/cloudwatch-appsignals-mcp-server) | On your machine (cloudscope-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 9, secrets among them: 2 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/alexpota/cloudscope-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.alexpota/cloudscope
Azure + GCP cost management: spending, forecasts, anomalies, budgets, idle resources, and tags.
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.alexpota/cloudscope As a local MCP server: npm package
claude mcp add --env "AZURE_CLIENT_SECRET=<YOUR_AZURE_CLIENT_SECRET>" --env "GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS>" --transport stdio cloudscope -- npx -y cloudscope-mcpRequires: AZURE_CLIENT_SECRET (secret), GOOGLE_APPLICATION_CREDENTIALS (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.alexpota/cloudscope publish no list of tools, so we do not compare tools.
Settings each asks for
Only Amazon CloudWatch Application Signals asks for
AWS_PROFILEAWS_REGION
Only io.github.alexpota/cloudscope asks for
AZURE_CLIENT_IDAZURE_CLIENT_SECRET (secret)AZURE_SUBSCRIPTION_IDAZURE_TENANT_IDGCP_BILLING_ACCOUNT_IDGCP_BILLING_TABLEGCP_PROJECT_IDGOOGLE_APPLICATION_CREDENTIALS (secret)GOOGLE_CLOUD_PROJECT
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.alexpota/cloudscope · 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.