AWS MCP Server

io.github.awsPublished by GitHub account awsv1.0.0-preview.0Updated Oct 24, 2026

AWS MCP Server lets AI securely access AWS using docs, API calls, and SOP workflows.

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

AI-generated overview

A local MCP server that lets an AI assistant securely access AWS through documentation, API calls and standard operating procedure workflows.

What you can do
Access AWS documentation and guidance while working in an assistant session, according to the registry description. Make AWS API calls on the user's behalf through the assistant. Follow standard operating procedure workflows for AWS tasks. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth considering when you want an assistant to look up AWS documentation, run AWS API operations, or follow defined AWS procedures from a desktop assistant session.
Requirements
Runs as a local process over stdio, installed from the PyPI package mcp-proxy-for-aws and launched with uvx, so a Python/uv runtime is needed. Desktop only; no web execution. The manifest declares no authentication, environment variables or headers, so how AWS credentials are supplied is not stated.
Before you install
The server is described as making AWS API calls, which can read or change cloud resources and may incur costs; review what it can reach before use. The manifest declares no authentication or credential variables, so confirm how AWS access is authorized. No tool list or README is provided, so the scope of its actions cannot be verified from this entry.

Installation

In SourceWeft

  1. Open AWS MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0-preview.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.