Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

AWS MCP Connector

by FerhatDundarversion 0.1.2i★ –iRuns on your computer
Registry nameio.github.FerhatDundar/aws-mcp-connector

Install

Overview

Description from the maker (original English)

MCP server for the AWS CLI. Read-only by default; single Go binary.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools
  • You need to fill in: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: AWS_PROFILE, AWS_REGION, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_MCP_ALLOW_WRITE, AWS_MCP_ALLOWED_SERVICES, AWS_MCP_CLI_PATH

Values marked secret are keys to your account. Never share them or paste them into a chat.

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

Fill in the empty values before running it.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • AWS_PROFILE env
    Named profile from ~/.aws/config to use. Leave unset to use the default profile.
  • AWS_REGION env
    Default AWS region if not set elsewhere.
  • AWS_ACCESS_KEY_ID secret env
    Static AWS access key. Only needed if not using a profile/SSO/role.
  • AWS_SECRET_ACCESS_KEY secret env
    Static AWS secret key. Only needed if not using a profile/SSO/role.
  • AWS_SESSION_TOKEN secret env
    Temporary session token, if using short-lived credentials.
  • AWS_MCP_ALLOW_WRITE env
    Set to "true" to permit mutating AWS CLI commands. Defaults to read-only.
  • AWS_MCP_ALLOWED_SERVICES env
    Optional comma-separated allowlist of AWS CLI service names (e.g. "s3,ec2"). Unset allows all.
  • AWS_MCP_CLI_PATH env
    Optional path to the aws binary. Defaults to "aws" resolved via PATH.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account FerhatDundar, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 5569 servers in this category
  • Published to the registry more recently than 27% of the other 5569 servers in this category
  • Basic checks equal to or better than 100% of the other 5569 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AWS MCP Connector safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 6 days ago

Computer or cloud

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 18 days ago

Runs on your computer

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

🔌 aws-mcp-connector

Talk to AWS CLI from an MCP-speaking agent.


A single static Go binary that speaks the Model Context Protocol and lets an agent run AWS CLI commands: any aws invocation, across every service the CLI supports, with a read-only-by-default safety gate on anything that mutates state.

No Python, no uv, no runtime dependency to install — just a binary and an .mcp.json. It shells out to the aws binary already installed and configured on the host (profile, SSO, IAM role, or static keys — whatever the AWS CLI's own credential chain resolves) instead of reimplementing the AWS SDK, so it gets the full breadth of the CLI for free rather than a hand-curated subset of services.

✨ Why this exists

An agent that only has a narrow, hand-picked set of AWS tools hits a wall

the moment you need something outside that set. This connector instead

wraps the AWS CLI itself, so an agent can run aws s3 ls, `aws ec2

describe-instances, aws iam list-users` — anything the CLI can do —

without waiting on a new tool to be written for it. Mutating commands are

blocked by default and require both a server-level opt-in and a per-call

confirm=true, so exploring/debugging is safe out of the box.

🧰 Tools

ToolWhat it doesWrite?
aws_execRun any aws ... command. Read-only by default — mutating commands need AWS_MCP_ALLOW_WRITE=true on the server *and* confirm=true on the call.✅ (gated)
aws_helpShow aws [subcommand] help text — always safe, use it to check exact syntax before calling aws_exec.
aws_whoamiShow the AWS identity (account, ARN, user/role) the configured credentials resolve to.
aws_list_profilesList named profiles configured in ~/.aws/config on the host.

Every tool accepts an optional response_format: markdown (default, pretty tables for a chat UI) or json (for programmatic use).

🚀 Quickstart

Fastest path: grab a prebuilt bundle from the latest release — download aws-mcp-connector-plugin- - - .zip, unzip it, and point Cowork/Claude at the plugin/ folder inside (see step 4 of SETUP.md). No Go toolchain required.

From source:

# 1. Build

cd go-server go mod tidy go build -o aws-connector-server . cp aws-connector-server ../plugin/servers/go/

2. Set up auth — needs the aws CLI itself installed and configured

(aws configure / aws sso login) — see SETUP.md

export AWS_PROFILE=default # optional, only if not using "default"

3. Run

./go-server/aws-connector-server # serves MCP over stdio

Or make build — see the Makefile for every shortcut (test, vet, fmt, lint, tidy).

Full walkthrough — including wiring this up as a Claude/Cowork plugin — is in [SETUP.md](SETUP.md).

🔐 Configuration

Everything is environment variables, passed through by the plugin's .mcp.json:

VariablePurposeDefault
AWS_PROFILENamed profile from ~/.aws/config to use.unset (default profile)
AWS_REGIONDefault region if not set elsewhere.AWS CLI's own default
AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY / AWS_SESSION_TOKENStatic credentials — only needed if not using a profile/SSO/role.unset
AWS_MCP_ALLOW_WRITE"true" to permit mutating commands at all (still needs confirm=true per call).false (read-only)
AWS_MCP_ALLOWED_SERVICESComma-separated allowlist of AWS CLI service names, e.g. "s3,ec2".unset (unrestricted)
AWS_MCP_CLI_PATHPath to the aws binary.aws resolved via PATH

🧪 Quality bar

This isn't a toy script — it's got the same checks you'd expect from a production Go service:

  • ✅ Unit tests for every input-validation path (go test ./...)
  • ✅ `go vet` + `gofmt` clean
  • ✅ [golangci-lint](https://golangci-lint.run/) (govet, staticcheck, errcheck, gosec, and more)
  • ✅ [govulncheck](https://go.dev/blog/vuln) — no known vulnerabilities in the dependency graph
  • ✅ [CodeQL](https://codeql.github.com/) static security analysis on every push
  • ✅ End-to-end verified against a real (or sandboxed) AWS CLI backend — not mocks
  • ✅ [Dependabot](.github/dependabot.yml) keeps Go modules and Actions current

All of it runs in CI on every push and PR.

🏷️ Releases & versioning

Versions follow semver and are cut automatically by release-please from Conventional Commits on main:

  • fix: ... → patch (v0.1.0 → v0.1.1)
  • feat: ... → minor (v0.1.1 → v0.2.0)
  • feat!: ... / BREAKING CHANGE: footer → major (v0.2.0 → v1.0.0)

Every merged PR updates a standing "chore(main): release vX.Y.Z" PR with an auto-generated CHANGELOG.md. Merging that PR:

  1. tags the release and publishes it on GitHub
  2. builds and attaches zipped, ready-to-install plugin bundles for linux/darwin/windows × amd64/arm64
  3. regenerates server.json from those exact assets (fresh version + SHA-256 hashes) and publishes it to the official MCP Registry via mcp-publisher, authenticated with GitHub OIDC — no stored secrets

See .github/workflows/release-please.yml and .github/workflows/publish-mcp-registry.yml (also runnable by hand for an existing tag via workflow_dispatch).

📁 Layout

aws-mcp-connector/

├── README.md ← you are here ├── SETUP.md ← step-by-step setup guide ├── CONTRIBUTING.md ← how to contribute ├── CODE_OF_CONDUCT.md ├── SECURITY.md ← vulnerability reporting ├── CODEOWNERS ├── LICENSE ← MIT ├── Makefile ← build / test / lint shortcuts ├── .golangci.yml ← lint rules ├── release-please-config.json ← semver/changelog automation config ├── .release-please-manifest.json ├── server.json ← MCP Registry manifest (regenerated fresh per release by CI) ├── scripts/ │ └── render-server-json.sh ← rebuilds server.json from a release's zip assets ├── .github/ │ ├── workflows/ │ │ ├── ci.yml ← build, vet, test, lint, govulncheck │ │ ├── codeql.yml ← security scanning │ │ ├── pr-title.yml ← Conventional Commits PR title check │ │ ├── release-please.yml ← version PRs, tagging, GitHub releases │ │ ├── publish-mcp-registry.yml ← publishes server.json to the MCP Registry │ │ └── rebuild-release-assets.yml ← manual re-attach fallback │ ├── ISSUE_TEMPLATE/ │ ├── PULL_REQUEST_TEMPLATE.md │ └── dependabot.yml ├── go-server/ ← the MCP server source │ ├── main.go │ ├── main_test.go │ ├── go.mod / go.sum │ └── README.md └── plugin/ ← installable Cowork/Claude plugin ├── .claude-plugin/plugin.json ├── .mcp.json ← holds credentials locally — never commit real ones └── servers/go/ ← compiled binary goes here

🤝 Contributing

PRs and issues are very welcome — see [CONTRIBUTING.md](CONTRIBUTING.md) for the full guide (setup, coding conventions, how to add a new tool) and the [Code of Conduct](CODE_OF_CONDUCT.md).

main is protected: every change, including the maintainer's, lands via pull request with CI green. PR titles must follow Conventional Commits — that's what drives the automatic versioning above.

Found a security issue? Please follow [SECURITY.md](SECURITY.md) instead of opening a public issue.

📄 License

MIT © FerhatDundar

Ask PopNx