Back to Directory/Cloud Providers

io.github.FerhatDundar/aws-mcp-connector

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

Cloud ProvidersGov0.1.2

πŸ”Œ aws-mcp-connector

Talk to AWS CLI from an MCP-speaking agent.

CI CodeQL Latest release MCP Registry Go Reference License: MIT MCP Conventional Commits PRs Welcome


A single static Go binary that speaks the Model Context Protocol and lets an agent run AWS CLI commands: any aws <service> <operation> 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 <service> <operation> ... 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 <service> [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-<version>-<os>-<arch>.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.

πŸ” 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 (govet, staticcheck, errcheck, gosec, and more)
  • βœ… govulncheck β€” no known vulnerabilities in the dependency graph
  • βœ… CodeQL static security analysis on every push
  • βœ… End-to-end verified against a real (or sandboxed) AWS CLI backend β€” not mocks
  • βœ… Dependabot 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 for the full guide (setup, coding conventions, how to add a new tool) and the Code of Conduct.

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 instead of opening a public issue.

πŸ“„ License

MIT Β© FerhatDundar

Setup from the maintainer

This listing does not have a supported local package template. Use the maintainer’s documentation for its hosted endpoint, authentication, and client-specific setup. No install command has been inferred.

Package

https://github.com/FerhatDundar/aws-mcp-connector/releases/download/v0.1.2/aws-mcp-connector-plugin-v0.1.2-darwin-arm64.zipother

Compatible MCP Clients

io.github.FerhatDundar/aws-mcp-connector works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More