AWS API MCP Server (AWS Labs)

90/100

Capped at 90: 1 of 2 real tool calls passed in our test; the tests add up to 100. Why scores are capped

Last tested 2026-11-13 UTC (Fresh: tested within 30 days) Working (tool call tested 2026-11-13 UTC) Connects without a key; tool calls need one

Advisories: not yet checked

Security review: not tested

Test points add up to 100; the score is capped at 90 because not every real tool call passed. Not a quality or security rating. Why scores are capped

Test points before the cap (100/100)

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs15/15
  • License10/10

Tested pypi awslabs-aws-api-mcp-server 1.6.0 (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 2 tools (2 annotated by the server: 1 read-only, 1 destructive). Real calls: 1 of 2 real function calls passed. Calls need AWS credentials for the core call_aws tool (aws s3 ls: Unable to locate credentials); suggest_aws_commands works without them.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): partial. 1 of 2 real function calls passed. Calls need AWS credentials for the core call_aws tool (aws s3 ls: Unable to locate credentials); suggest_aws_commands works without them. Evidence: local test run, Nov 13, 2026 UTC.

Transport (tested 2026-11-13 UTC): stdio

Token cost (estimate): approx. 1493 tokens, cl100k estimate (2 tools, measured 2026-11-13 UTC, version 1.6.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 0 read, 1 write (state-changing), 1 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown

Auth: API key. Rate limit: unknown. Pricing unit: unknown.

  • call_aws — unclassified
  • suggest_aws_commands — write (state-changing)

listing-flags calls_need_key or auth_kind

Score 90/100 · Tools 2 · Token cost approx. 1,493 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 1.6.0 · Package awslabs-aws-api-mcp-server · Repo awslabs/mcp

Summary: AWS API MCP Server (AWS Labs) completed an MCP handshake without credentials and exposed 2 tools.

Evidence summary

Handshake
pass
Tools listed
2
Context cost
approx. 1493 tokens, cl100k estimate (2 tools, measured 2026-11-13 UTC, version 1.6.0; 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

TestResultPointsEvidence
installpass20uv pip install awslabs-aws-api-mcp-server (Python venv, Linux) succeeded in 1s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 2 tools listed in 14.9s.
maintenancepass25Repo pushed 0 days before test; 9,913 GitHub stars.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)).
licensepass10Apache-2.0 (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 1493 tokens, cl100k estimate for 2 tools · about 18% 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 2 tools (Method details: MCP initialize then tools/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)

19c2aa7bb23c: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "awslabs-aws-api-mcp-server",
  "version": "1.6.0",
  "registry": "pypi",
  "status": "working",
  "tested": "2026-11-13",
  "tools_count": 2,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`uv pip install awslabs-aws-api-mcp-server` (Python venv, Linux) succeeded in 1s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 2 tools listed in 14.9s."
    ],
    "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-aws-api-mcp-server

Pin the version we tested

uvx --from awslabs-aws-api-mcp-server==1.6.0 awslabs.aws-api-mcp-server

pip install awslabs-aws-api-mcp-server==1.6.0

tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "aws-api-mcp-server-aws-labs": {
      "command": "uvx",
      "args": [
        "--from",
        "awslabs-aws-api-mcp-server==1.6.0",
        "awslabs.aws-api-mcp-server"
      ]
    }
  }
}

Tools listed

suggest_aws_commands, call_aws

Quick config

{
  "mcpServers": {
    "aws-api-mcp-server-aws-labs": {
      "command": "uvx",
      "args": [
        "awslabs-aws-api-mcp-server"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run uv pip install awslabs-aws-api-mcp-server (Python venv). This is the exact command we ran on 2026-11-13 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (2 in our test).
{
  "mcpServers": {
    "aws-api-mcp-server-aws-labs": {
      "command": "uvx",
      "args": [
        "awslabs-aws-api-mcp-server"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best cloud MCP servers

FAQ

Is AWS API MCP Server (AWS Labs) deprecated?

No. awslabs-aws-api-mcp-server was not deprecated or archived when we last tested it on 2026-11-13 UTC.

What replaces AWS API MCP Server (AWS Labs)?

Nothing; AWS API MCP Server (AWS Labs) is not deprecated as of 2026-11-13 UTC.

Does AWS API MCP Server (AWS Labs) need an API key?

It connects and lists 2 tools without a key, but its tool calls need one.

Embed the badge

TestedMCP: 90/100, tested 2026-11-13 UTC

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.

Claim this listing · Report an issue