Skip to content

docs(aws-api-mcp-server): mark aws___call_aws as removed in MIGRATION.md (#4581) - #4584

Open
warren830 wants to merge 1 commit into
awslabs:mainfrom
warren830:fix/4581-migration-remove-call-aws
Open

docs(aws-api-mcp-server): mark aws___call_aws as removed in MIGRATION.md (#4581)#4584
warren830 wants to merge 1 commit into
awslabs:mainfrom
warren830:fix/4581-migration-remove-call-aws

Conversation

@warren830

@warren830 warren830 commented Sep 4, 2026

Copy link
Copy Markdown

Issue

Fixes #4581.

Problem

src/aws-api-mcp-server/MIGRATION.md still lists aws___call_aws as a live tool on the AWS MCP Server and says every action is "reachable through aws___call_aws and aws___run_script". AWS removed aws___call_aws from the managed server on 2026-08-31 (tools/call now returns The call_aws tool has been removed, use another one.). Clients built from this guide break with a hard-to-diagnose error while the guide tells readers the tool is fine.

Changes

  1. Removed aws___call_aws from the live tool table and added a dated removal note (deprecated 2026-07-15, removed 2026-08-31) pointing to aws___run_script.
  2. Rewrote the API coverage section to name aws___run_script only.
  3. Added a call_awsrun_script porting example, with the two notes that trip up most ports:
    • call_boto3 takes the PascalCase operation name (GetSecretValue), not the CLI's get-secret-value;
    • a single-call run_script takes ~13–15s, so clients ported with a 10s timeout fail on every call.

Docs-only change; no code paths touched.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

….md (awslabs#4581)

AWS removed aws___call_aws from the managed AWS MCP Server on 2026-08-31, but the migration guide still listed it as a live tool and told readers every action is reachable through it. Clients built from the guide broke with a hard-to-diagnose 'The call_aws tool has been removed' error. Remove it from the live tool table (replaced by a removal note), point API coverage at aws___run_script only, and add a call_aws->run_script porting example noting call_boto3 takes the PascalCase operation name and that a single-call run_script takes ~13-15s (so 10s client timeouts fail).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: To triage

Development

Successfully merging this pull request may close these issues.

(aws-api-mcp-server): MIGRATION.md lists aws___call_aws as a live tool, AWS removed it on 2026-08-31

1 participant