AWS CloudWatch MCP Server (AWS Labs)
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested pypi awslabs-cloudwatch-mcp-server 0.3.1 (Apache-2.0; repo awslabs/mcp). Installed pinned with scripts off (uv venv, Python 3.13) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 19 tools (no tool annotations). Real calls: 0 of 3 real function calls passed. Calls need AWS credentials. Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. Calls need AWS credentials. Evidence: local test run, Nov 13, 2026 UTC.
Transport (tested 2026-11-13 UTC): stdio
Token cost (estimate): approx. 11943 tokens, cl100k estimate (19 tools, measured 2026-11-13 UTC, version 0.3.1). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 12 read, 1 write (state-changing), 6 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown
Auth: API key. Rate limit: unknown. Pricing unit: unknown.
analyze_log_group— readanalyze_metric— unclassifiedcancel_logs_insight_query— write (state-changing)describe_log_groups— readexecute_cwl_insights_batch— unclassifiedexecute_log_insights_query— readexecute_promql_query— unclassifiedexecute_promql_range_query— unclassifiedget_active_alarms— readget_alarm_history— readget_logs_insight_query_results— readget_metric_data— readget_metric_metadata— readget_promql_label_values— readget_promql_labels— readget_promql_series— readget_recommended_metric_alarms— readrecommend_indexes_account— unclassifiedrecommend_indexes_loggroup— unclassified
listing-flags calls_need_key or auth_kind
Score 70/100 · Tools 19 · Token cost approx. 11,943 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 0.3.1 · Package awslabs-cloudwatch-mcp-server · Repo awslabs/mcp
Summary: AWS CloudWatch MCP Server (AWS Labs) completed an MCP handshake without credentials and exposed 19 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 19
- Context cost
- approx. 11943 tokens, cl100k estimate (19 tools, measured 2026-11-13 UTC, version 0.3.1; an estimate) ranking · add up your servers' context cost
- API key
- Connects without a key; tool calls need one
- Tested
- 2026-11-13 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install awslabs-cloudwatch-mcp-server (Python venv, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 19 tools listed in 8.4s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 9,913 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 11943 tokens, cl100k estimate for 19 tools · about 146% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-13 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 19 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
9c2c6d907c1d: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "awslabs-cloudwatch-mcp-server",
"version": "0.3.1",
"registry": "pypi",
"status": "working",
"tested": "2026-11-13",
"tools_count": 19,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`uv pip install awslabs-cloudwatch-mcp-server` (Python venv, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 19 tools listed in 8.4s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 9,913 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
}
}Install
uvx awslabs-cloudwatch-mcp-server
Pin the version we tested
uvx --from awslabs-cloudwatch-mcp-server==0.3.1 awslabs.cloudwatch-mcp-server
pip install awslabs-cloudwatch-mcp-server==0.3.1
tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"aws-cloudwatch-mcp-server-aws-labs": {
"command": "uvx",
"args": [
"--from",
"awslabs-cloudwatch-mcp-server==0.3.1",
"awslabs.cloudwatch-mcp-server"
]
}
}
}Tools listed
describe_log_groups, analyze_log_group, execute_log_insights_query, get_logs_insight_query_results, cancel_logs_insight_query, execute_cwl_insights_batch, recommend_indexes_loggroup, recommend_indexes_account, get_metric_data, get_metric_metadata, analyze_metric, get_recommended_metric_alarms, execute_promql_query, execute_promql_range_query, get_promql_label_values, get_promql_series, get_promql_labels, get_active_alarms, get_alarm_history
Quick config
{
"mcpServers": {
"aws-cloudwatch-mcp-server-aws-labs": {
"command": "uvx",
"args": [
"awslabs-cloudwatch-mcp-server"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
uv pip install awslabs-cloudwatch-mcp-server(Python venv). This is the exact command we ran on 2026-11-13 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (19 in our test).
{
"mcpServers": {
"aws-cloudwatch-mcp-server-aws-labs": {
"command": "uvx",
"args": [
"awslabs-cloudwatch-mcp-server"
]
}
}
}Test history
- 2026-11-13 UTC: New
FAQ
Is AWS CloudWatch MCP Server (AWS Labs) deprecated?
No. awslabs-cloudwatch-mcp-server was not deprecated or archived when we last tested it on 2026-11-13 UTC.
What replaces AWS CloudWatch MCP Server (AWS Labs)?
Nothing; AWS CloudWatch MCP Server (AWS Labs) is not deprecated as of 2026-11-13 UTC.
Does AWS CloudWatch MCP Server (AWS Labs) need an API key?
It connects and lists 19 tools without a key, but its tool calls need one.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.