Add the AWS (AWS Labs) MCP server to VS Code

Config last verified Jun 1, 2026

The exact config to run AWS (AWS Labs) in VS Code — paste it in, restart, and the tools load.

Prerequisites

VS Code installed.

Setup

1. Open `.vscode/mcp.json`

2. Add this configuration

Add to .vscode/mcp.json

.vscode/mcp.json

json

{
  "servers": {
    "aws": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "awslabs.aws-api-mcp-server@latest"
      ],
      "env": {
        "AWS_REGION": "<AWS_REGION>",
        "AWS_API_MCP_PROFILE_NAME": "<AWS_API_MCP_PROFILE_NAME>",
        "READ_OPERATIONS_ONLY": "<READ_OPERATIONS_ONLY>"
      }
    }
  }
}

Heads up

VS Code uses the `servers` key (not `mcpServers`) and requires `type`.

3. Restart VS Code and confirm the AWS (AWS Labs) tools load.

Gotchas

VS Code uses the `servers` key (not `mcpServers`) and requires `type`.

VS Code is the exception to every other client: its top-level key is "servers", not "mcpServers", and each entry needs an explicit "type" (for example "http" or "stdio"). Secrets are not inlined; instead you declare an "inputs" array and reference each value as ${input:id}, so VS Code prompts for it once and never writes it to disk. Remote servers connect natively with OAuth.

← Back to the AWS (AWS Labs) MCP server