Share AWS API MCP tools.
AWS CLI command suggestions and execution — every call runs against your account, so nothing is allowed by default.
Run on your machine
Start the server on your host machine. Tools not listed in --allow are completely hidden from the agent.
npx -y @mcpwire/cli share \
--name aws-api \
--allow "" \
--redact-secrets \
-- uvx awslabs.aws-api-mcp-server==1.5.6
Exposes 0 default tools with pattern-based secret redaction.
Optionally set an expiry with --ttl 30m, prompt for approvals with --confirm, or limit calls with --max-calls 20.
Connect your teammate’s agent
MCPWire prints a unique wire://... ticket in your terminal. Send it privately to your teammate to paste into their MCP client:
Claude Desktop · Cursor · Windsurf config
{
"mcpServers": {
"aws-api": {
"command": "npx",
"args": [
"-y",
"@mcpwire/cli",
"join",
"wire://<TICKET_FROM_HOST>"
]
}
}
}
Replace <TICKET_FROM_HOST> with the active session ticket. The agent can only discover and call the tools exposed above.
Scoped tool permissions
MCPWire acts as a Layer 7 JSON-RPC firewall. Requests for blocked tools are dropped on the wire before ever touching your machine.
| Tool | Default Policy | Notes |
|---|---|---|
suggest_aws_commands | Blocked (Review) | Suggests AWS CLI commands for a natural-language request — suggestions only, nothing executes. |
call_aws | Blocked (High risk) | Executes an AWS CLI command with the host's credentials. Can read, modify, or delete anything the credentials allow. |
Test and verify
Try these recommended prompts to confirm the agent receives expected outputs and that restricted actions fail safely.
Try AWS API
Configure AWS credentials on the host the usual way (AWS_PROFILE or the standard environment chain). This is the official AWS Labs server that executes real AWS CLI commands — which is why this guide starts with every tool denied. The share command prints an explicit empty allowlist, and the guest must ask for approval on each call.
A good session flow: let the guest plan with suggest_aws_commands (it only suggests), then approve individual call_aws invocations you have read. If you want a more open session, re-share with --allow suggest_aws_commands and keep call_aws on manual approval, or add it for read-only commands you trust. The credentials decide the blast radius — use a scoped role, not an admin key.
The generated command above contains the catalog’s explicit default allowlist. Check the guest’s tool list before making calls and use the server’s argument schema for required fields. See the CLI guide for guest configuration and session controls for approvals, redaction, and expiry.
--record session.wirelog to your host command. Drop the resulting file into the Session Replay Viewer to inspect timestamps, latency, blocked attempts, and secret scrubbing.