PlugWiki
CloudBurn logo

CloudBurn MCP Server: Setup for Claude, Codex and Other Apps

OfficialLocal
Getnpm@cloudburn/mcptowardsthecloud/cloudburn
Tools
4
3 read · 1 change
Downloads
253
a week
Works in
12
apps
Risk
Low
read only
Auth
None

Lets Claude, Codex and other assistants find AWS cost waste in Terraform, CloudFormation and live AWS accounts.

CloudBurn's MCP server lets your assistant scan Terraform and CloudFormation files for AWS cost problems, and check a live AWS account through read-only calls. It runs on your computer and needs Node.js 24 or later. Scanning code needs no AWS login. Live checks use the AWS profile in your environment, so give it a read-only one.

Good for

  • Platform and DevOps engineers reviewing infrastructure code for cost
  • FinOps teams checking live AWS accounts for waste
  • Developers who want cost checks before they deploy

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install CloudBurn MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the CloudBurn MCP server to Claude Code. Run this command:

claude mcp add cloudburn -- npx -y @cloudburn/mcp

Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js 24 or later.

Read-only mode: All four tools are marked read-only. discover writes only a local evidence cache.

Needs Node.js 24 or later. Scanning Terraform and CloudFormation files needs no AWS account. For live checks, set AWS_PROFILE and AWS_REGION where the app starts the server and run npx -y cloudburn discover init once to set up AWS Resource Explorer. The README names the Claude Code and Codex commands; configs for other apps use the README's generic command and are adapted by PlugWiki.

From the project README. Source.

Tools

  • Scans Terraform or CloudFormation files for AWS cost waste

    Reads a Terraform file, CloudFormation template or a folder of them and lists cost findings by rule, with file locations. It needs no AWS credentials. The path must be absolute.

    Try: “Scan /Users/me/infra for AWS cost issues before I deploy.”

    Files · scan_iac

  • Checks your live AWS resources in one region for cost waste

    Evaluates running resources in a region using read-only AWS calls and the AWS Resource Explorer. It can run up to five minutes and reuses a local evidence cache shared with the CloudBurn CLI.

    Try: “Find cost waste in my us-east-1 account.”

    Write · discover

  • Shows whether AWS Resource Explorer is set up for live checks

    Reports the Resource Explorer index status across regions for your current AWS credentials, so you know why a live check is incomplete.

    Try: “Is AWS Resource Explorer set up for live discovery?”

    Network · discovery_status

  • Lists the built-in cost rules

    Returns rule IDs with their AWS service, severity and whether they apply to code scans or live checks, with filters.

    Try: “List the high severity EC2 cost rules.”

    Read · list_rules

Read from the source code

Permissions

low risk · 3 things to watch

Low risk

The assistant can read infrastructure code and, with AWS credentials, read your AWS resources, but cannot change anything. Use a read-only AWS profile.

What it can do

Watch out for

  • Reads any file path it is given

    The scan tool takes an absolute path and is not limited to a project folder, so it can read Terraform or CloudFormation files anywhere your account can. Point it only at infrastructure code. github.com

  • Live checks use your AWS credentials

    The discover tools use the AWS profile in the environment that starts the server. The README says the server never changes AWS resources, so use a read-only AWS profile. github.com

  • It keeps a local evidence cache

    Live results are cached under your cache folder and shared with the CloudBurn CLI. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyAll four tools are read-only by design: the README says the server never changes AWS resources.
Talks toAWS APIs, only for live discovery
Sign-in and keysNo account. Live discovery uses your standard AWS credentials (AWS_PROFILE, AWS_REGION).

Questions

Is the CloudBurn MCP server official?

Yes. It is published by the CloudBurn project in its own repository, alongside the CloudBurn CLI and SDK.

Do I need AWS credentials?

Only for live checks. Scanning Terraform or CloudFormation files needs none. Live checks use the standard AWS credential chain of the process that starts the server.

Can it change my AWS account?

No. The README says the server never changes AWS resources, and all four tools are marked read-only.

What do I need installed?

Node.js 24 or later. For live checks you also run npx -y cloudburn discover init once to set up AWS Resource Explorer, per the README.

Is there a Claude Code plugin?

Yes. The README documents a CloudBurn plugin for Claude Code and Codex that bundles this server with a skill. The server alone is in the install box.

Does it run locally?

Yes. It runs on your computer over stdio. Only live discovery calls AWS.

How do I add it to Claude Code?

Use the Claude Code tab in the install box above.

Information

updated Nov 2, 2026

Publisher
Official
Package
@cloudburn/mcp
Registry
npm
Transport
stdio
Auth
None
Version
0.1.10
License
Apache-2.0
Last commit
Oct 30, 2026
Open issues
54

WebsiteGitHubnpmChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 3
  1. github.com · github.com
  2. github.com · github.com
  3. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.