Open Source MCP Servers for AWS for VS Code: Setup & Config

What you can do with Open Source MCP Servers for AWS in VS Code

Choose task-specific AWS context and workflow integrations from a broad open-source server collection.

• Provide an assistant with current AWS documentation and service guidance.
• Add AWS data and analytics context to an AI application.

Before you start: Open Source MCP Servers for AWS in VS Code

• An MCP-compatible client
• uvx for the documentation-server example

This is the AWS Documentation MCP Server configuration encoded in the README's installation link, not a command for the entire suite. The linked example uses ERROR logging and the aws documentation partition. Configure other servers separately; individual tool identifiers are not stated in the supplied excerpt.

Open Source MCP Servers for AWS VS Code configuration

1. Choose VS Code configuration scope

   For Open Source MCP Servers for AWS, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Open Source MCP Servers for AWS to VS Code

   Use the mcp entry below in servers. Keep Open Source MCP Servers for AWS's documented stdio connection fields and your other VS Code entries.

3. Check Open Source MCP Servers for AWS in VS Code

   Open Source MCP Servers for AWS: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "awslabs.aws-documentation-mcp-server@latest"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "<desired logging level>",
        "AWS_DOCUMENTATION_PARTITION": "<AWS documentation partition>"
      }
    }
  }
}

Troubleshooting Open Source MCP Servers for AWS in VS Code

• Make uvx awslabs.aws-documentation-mcp-server@latest (from uv, for Python tools) available in the workspace, container, or remote environment hosting Open Source MCP Servers for AWS. Start through VS Code's MCP controls; inspect output and trust prompts.
• For Open Source MCP Servers for AWS, keep AWS_DOCUMENTATION_PARTITION, FASTMCP_LOG_LEVEL out of version control; VS Code documents input variables and secret handling.
• Open Source MCP Servers for AWS uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: The repository describes local servers as stdio-only and removed SSE from current major versions.
• Known limitation: Production agent builders are directed toward the newer Agent Toolkit for AWS.
• Known limitation: A single universal tool catalog and launch command are not provided in the supplied excerpt.
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions