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

Amazon Web Services MCP

by servosityversion 0.1.9i★ –iRuns on your computer
Registry nameio.github.Servosity/aws-billing-mcp

Install

Overview

Description from the maker (original English)

Get a non-expert from zero to a Slack-delivered, plain-English, waste-flagged AWS bill breakdown

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, AWS_BILLING_MCP_HTTP_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_ACCESS_KEY_ID, AWS_BILLING_BASE_URL, AWS_BILLING_SLACK_CHANNEL, AWS_REGION, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_PROFILE, AWS_BILLING_MCP_READ_ONLY, AWS_BILLING_NO_LOCAL_DATA, AWS_BILLING_USER_AGENT, AWS_BILLING_MCP_HTTP_TOKEN

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_ACCESS_KEY_ID secret required env
    Access key ID for an IAM principal with Cost Explorer read access. Resolved by the AWS SDK's default credential chain.
  • AWS_BILLING_BASE_URL env
    Base URL for the AWS Billing Intelligence API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
  • AWS_BILLING_SLACK_CHANNEL env
    Slack channel or DM ID that `report --slack` posts to by default (the --slack-channel flag overrides it). Leave blank to pass the destination on every run.
  • AWS_REGION env
    Region for the EC2, CloudWatch and S3 calls. Cost Explorer is always served from us-east-1 regardless of this value.
  • AWS_SECRET_ACCESS_KEY secret required env
    Secret access key paired with AWS_ACCESS_KEY_ID.
  • AWS_SESSION_TOKEN secret env
    Session token, required only when the keys above are temporary STS or SSO credentials. Leave blank for long-lived IAM user keys.
  • AWS_PROFILE env
    Optional. Name of a profile in ~/.aws/config (SSO, assume-role or credential_process).
  • AWS_BILLING_MCP_READ_ONLY env
    Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.
  • AWS_BILLING_NO_LOCAL_DATA env
    Optional. Set to 1 to keep no local copy of API responses: reads go to the API instead of the local store.
  • AWS_BILLING_USER_AGENT env
    Overrides the User-Agent the CLI sends on its own HTTP requests.
  • AWS_BILLING_MCP_HTTP_TOKEN secret env
    Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.

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 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account servosity, 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 1395 servers in this category
  • Published to the registry more recently than 100% of the other 1395 servers in this category
  • Basic checks equal to or better than 100% of the other 1395 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 Amazon Web Services MCP 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, AWS_BILLING_MCP_HTTP_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.9) reached the registry today.

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:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by 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.

Computer or cloud★ 34,245MITUpdated 4 days ago
Install

Desktop Commander

by wonderwhy-er

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

Runs on your computer★ 10,225MITUpdated 16 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

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.

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.

Full skill page - install, outcomes, safety model.

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):

Your AI agentHow to install the Amazon Web Services skill
Claude DesktopRun installer, then Settings > Extensions to register aws-billing-mcp (no JSON editing).
ChatGPT (desktop app)Run installer, then add aws-billing-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet.
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add aws-billing-mcp to mcp.json under the servers key, then pick Agent mode.

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.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Google GeminiGemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills 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](../../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](./mcp-install.md) and [docs/which-agent.md](../../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

Question your MSP keeps askingCommand
Why did my bill change month-over-month?aws-billing-cli compare --from last-month --to this-month
Which linked account is driving org spend?aws-billing-cli consolidated --period this-month
Where am I wasting money right now?aws-billing-cli waste rank
Where is my data-transfer cost leaking?aws-billing-cli waste transfer --period last-month
What does this cryptic usage-type line mean?aws-billing-cli explain EUC1-DataTransfer-Out-Bytes
What will I spend next month?aws-billing-cli forecast --profile-aws prod
How do I give a colleague read-only billing access?aws-billing-cli iam-setup --tier core --format cloudformation
What's a plain answer about my bill?aws-billing-cli ask "what are my top services"

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

Only the beginning is shown; read the rest in the repo

Ask PopNx