Amazon Web Services MCP

Amazon Web Services + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Amazon Web Services API. Not affiliated with, endorsed by, or sponsored by Amazon.com, Inc. or its affiliates.

[AWS demo - animated preview]

_{▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.}

Get a non-expert from zero to a Slack-delivered, plain-English, waste-flagged AWS bill breakdown, and cache it so you don't pay per Cost Explorer call. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

Security note (until this connector is reprinted). Do not run HTTP mode (--transport http), not even on localhost. This build has no password, listens on every network interface, and predates the browser-rebinding guard, so a web page you open can reach it. The MCP tools can also read your data with your credentials. Use the default stdio transport. If you set up a tunnel for a remote agent, shut it down. A fix is on the way.

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs aws-billing-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly and speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: docs/which-agent.md.

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion aws-billing-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set AWS_BILLING_CLI_PATH to an existing binary). Details: #331.

Download Amazon Web Services MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Amazon Web Services release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills/plugin install aws-billing@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Amazon Web Services Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/aws-billing/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/aws-billing/install.ps1 | iex. Then authenticate per the README and run aws-billing-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/aws-billing/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/aws-billing/install.sh)

The installer drops both aws-billing-cli (the CLI) and aws-billing-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

aws-billing-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/aws-billing/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/aws-billing/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update aws-billing@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see mcp-install.md and docs/which-agent.md for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/aws-billing --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/aws-billing --force

Hermes speaks MCP natively, so it can also use the aws-billing-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the aws-billing skill from https://github.com/servosity/msp-skills/tree/main/skills/aws-billing. The skill defines how its required CLI (aws-billing-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

See mcp-install.md for the credentials aws-billing-cli needs.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Amazon Web Services integrations and MCP servers proxy each question into a live Cost Explorer call. That's fine for one lookup - but each request costs $0.01, and it dies the moment you're asking "which of my linked accounts had the biggest cost jump this quarter, and what service drove it" across every account at once.

This skill syncs Amazon Web Services into a local SQLite mirror with full-text search. Aggregate questions become one local query: instant, offline, and the AI sees the ranked answer, not the raw data. Compound commands like consolidated, compare, and waste rank join across linked accounts, services, and resource inventory - work a stateless API wrapper can't do without paying per call.

The pain this closes

On r/msp, the recurring AWS thread is some version of "the client's bill jumped and I can't tell them why." The console shows a wall of usage-type codes like EUC1-DataTransfer-Out-Bytes, and Cost Explorer answers the question you didn't ask - buy Reserved Instances - instead of the one you did: what moved, and where is money leaking? Corey Quinn's Last Week in AWS has built an audience on the premise that AWS billing is opaque by design. For an MSP managing AWS for clients, that opacity is a monthly tax: the cost review gets skipped because nobody can read the bill, and the waste compounds until the number is already a surprise.

This skill closes that with a handful of high-leverage commands:

• aws-billing-cli compare - ranks the services that moved month-over-month, so "why did it change?" is a sentence, not a spreadsheet.
• aws-billing-cli consolidated - resolves every linked account by name with an inline delta, so you can name the account driving org spend in one view.
• aws-billing-cli waste rank - one dollar-ranked table of idle EC2, unattached EBS, orphaned snapshots, and unassociated Elastic IPs, with a grand total you could save.
• aws-billing-cli waste transfer - names where cross-AZ, cross-region, and NAT-gateway data-transfer cost is leaking.
• aws-billing-cli explain - decodes an opaque usage-type string into plain English.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way aws-billing-mcp runs, and shares MCP configuration with Codex (OpenAI): add aws-billing-mcp under Settings > MCP servers as a STDIO server, or add it once to Codex's ~/.codex/config.toml. ChatGPT on the web is not supported by msp-skills yet: it needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted; the security note in mcp-install.md explains why. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Does this work with Codex, Cursor, Windsurf, Cline, Copilot, or Gemini?

Yes - all of them speak MCP. Cross-tool install commands are in the matrix above and the deep-dive in docs/which-agent.md.

Do I need to know how to code?

No. The recommended install is to paste one sentence into Claude Code or Codex - your agent reads SKILL.md and does the install. The fallback is a one-line installer per OS (bash or PowerShell). Neither path requires writing code. You'll enter your Amazon Web Services credentials once.

Is my Amazon Web Services data safe?

Your data stays on your machine. The CLI and MCP server are local binaries. The SQLite mirror sits in a directory under your user account. The AI agent only sees what the CLI returns - typically a query result, not raw bulk data. Credentials are read from your environment or your agent's config; never bundled into this repo or transmitted anywhere by MSP Skills.

Will this run up my Cost Explorer bill?

No - that's the point of the local cache. sync pulls your cost data once (each Cost Explorer request is about $0.01), then bill, compare, consolidated, waste, and ask answer from the local SQLite mirror for free. Pass --data-source live only when you want a fresh pull.

Do I need the aws CLI installed?

No. The binary signs its own AWS requests (SigV4) using the native credential chain - environment variables, a shared --profile-aws, SSO, or assume-role (EC2 instance-metadata credentials are not used; on EC2 use a profile, SSO or environment keys). There's nothing to paste and no aws CLI dependency.

Does it work from a member account, or only the payer?

Org-wide cost data (the consolidated rollup) needs a management/payer-account profile; from a member account you see only that account's own costs. Resource-level waste scans work in any account. Run aws-billing-cli doctor to see which profile, region, and credential source resolved. Credentials here come from the AWS SDK chain rather than a base URL, so doctor reports not verified instead of claiming the credential works; run aws sts get-caller-identity, or any read command below, to prove it end-to-end.

Can it change anything in my AWS account?

No. Every command is read-only against the AWS billing & Cost Explorer API - it never stops, deletes, modifies, or buys anything. waste gp2-gp3 even prints the aws ec2 modify-volume command you would run rather than running it. The opt-in outbound network actions are report --post-slack (posts a summary to Slack), feedback --send (sends a feedback note upstream, and only if you set AWS_BILLING_FEEDBACK_ENDPOINT), and --deliver webhook:<url> (POSTs a command's output to a URL you name) - none of them changes anything in AWS, and even the generic import command can't, because the billing API exposes no write endpoint.

What does it cost?

Free. Apache-2.0 licensed. You pay only for whichever AI agent you use (Claude, ChatGPT, Codex, etc.), and that's billed by your AI provider, not by us.

Safety model

The strongest control is the scope you grant the Amazon Web Services credentials - the CLI can only do what the credentials are permitted to do. Full details, including how to lock it down, are in governance.md.

Status

Live-verified. Confirmed by Servosity (maintainer) against their own production tenant. More MSPs run it live in our weekly Build Sessions. RSVP at compoundingteams.com/build-sessions.

Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).

Maintained by Servosity. Apache-2.0 licensed. Built with CLI Printing Press. Last updated: 2026-06-30.