Which AI clients can use the AWS (local CLI) MCP server?

19 AI clients, including Cursor, VS Code, and Claude Code. AWS (local CLI) runs on the user’s machine, and the client reaches it through the Runlayer CLI.

Which AWS (local CLI) tools are available?

AWS (local CLI) exposes 2 tools, including Suggest AWS CLI commands, Execute AWS CLI commands. 1 only read data and 1 can change or delete it. Admins choose which ones each group can call.

How does AWS (local CLI) authenticate?

Sign in the way AWS (local CLI) requires. Runlayer holds the credentials so they stay out of the client’s configuration.

Integrations / MCP servers

AWS (local CLI)

Local AWS MCP server (awslabs.aws-api-mcp-server) wrapping the AWS CLI.

Book a demo View documentation

Tools

2 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

Search 2 tools

Suggest AWS CLI commands
Read only
Tool name: suggest_aws_commands
Suggest AWS CLI commands based on a natural language query.
Execute AWS CLI commands
Destructive
Tool name: call_aws
The command MUST start with "aws" and follow AWS CLI syntax

Compatibility

Connect AWS (local CLI) to the clients your teams already use

19 AI clients can connect to AWS (local CLI) through Runlayer. Pick one for its setup steps and controls.

Cursor VS Code Claude Code Windsurf Goose Codex Hermes Raycast Warp GitHub Copilot GitHub Copilot CLI Gemini CLI Zed Cline CLI Antigravity OpenCode Crush ECA Oh My Pi

Why Runlayer

Why connect AWS (local CLI) through Runlayer?

One approved path

Approve AWS (local CLI) once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.