Infracost MCP server
io.github.DownAtTheBottomOfTheMoleHole/infracost·v1.0.1MCP server for Infracost CLI integration - cloud cost estimates for Infrastructure as Code
0 stars
Reviews
Write oneNobody has reviewed Infracost yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Infracost tools (8, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
infracost_authAuthenticate with Infracost Cloud. Opens browser for login flow.
infracost_breakdownGenerate cost breakdown for Infrastructure as Code (Terraform, CloudFormation, etc.). Shows cost estimates for cloud resources.
infracost_commentwrite actionPost cost estimate comments to pull requests on GitHub, GitLab, Azure Repos, or Bitbucket.
infracost_configureGet or set Infracost configuration options (API key, currency, etc.).
infracost_diffShow cost diff between current IaC and planned changes. Useful for pull request reviews to understand cost impact.
infracost_generate_usageGenerate Infracost usage file with sensible defaults for specified resource types. Complements infracost_configure by providing pre-filled templates.
infracost_outputFormat Infracost JSON output to different formats (table, html, github-comment, etc.).
infracost_uploadwrite actionUpload Infracost JSON output to Infracost Cloud for centralized cost visibility and reporting.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- Code scan6 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How Infracost compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 94/100
- higher than 96% of 48,255 servers
- Tools
- 8
- the typical server has 7
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 6 read · 2 change
Install Infracost in Claude Code, Cursor or VS Code
Runs npx -y @downatthebottomofthemolehole/infracost-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add infracost -- npx -y @downatthebottomofthemolehole/infracost-mcp-server
What the publisher says
From the Infracost repository's README, as published. We do not edit it. Read it on GitHub
Infracost MCP Server
<!-- mcp-name: io.github.downatthebottomofthemolehole/infracost -->
Note: This is a community-maintained MCP server. It is not an official Model Context Protocol server from Infracost.
A Model Context Protocol (MCP) server for running the Infracost CLI to estimate, compare, and publish infrastructure cost changes from Terraform and other Infrastructure as Code projects.
Overview
This server provides eight MCP tools across estimation, reporting, collaboration, and operations workflows:
- infracost_breakdown to generate baseline cost estimates.
- infracost_diff to compare planned cost changes.
- infracost_output to render existing Infracost JSON in different formats.
- infracost_comment to post PR comments on supported SCM platforms.
- infracost_upload to upload reports to Infracost Cloud.
- infracost_configure to get or set CLI configuration.
- infracost_auth to run authentication flow.
- infracostgenerateusage to generate usage files with sensible defaults.
Platform Compatibility
This MCP server is platform-agnostic and works in local and CI environments:
- Local development
- GitHub Actions
- GitLab CI/CD
- Azure DevOps
- CircleCI, Jenkins, and Bitbucket Pipelines
- AI Agents and Copilot workflows
The primary requirements are Node.js and the Infracost CLI binary.
Tool Matrix
Tools
infracost_breakdown
Runs infracost breakdown.
Inputs:
- workingDirectory (string, optional): Command working directory.
- path (string, optional): Path to Terraform/IaC directory or plan JSON.
- configFile (string, optional): Path to Infracost config file.
- usageFile (string, optional): Path to usage file.
- format (string, optional): Output format. Default: table.
- fields (string[], optional): Fields to include in output.
- showSkus (boolean, optional): Include SKU details.
- syncUsageFile (boolean, optional): Sync usage file with detected resources.
- compareTo (string, optional): Baseline Infracost JSON path.
- terraformWorkspace (string, optional): Terraform workspace.
- terraformPlanFlags (string, optional): Flags for terraform plan.
- timeoutSeconds (number, optional): Timeout in seconds.
infracost_diff
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Infracost: common questions
- Is Infracost MCP server safe?
- Yes, by our scan: it is graded A (94/100). Read the Infracost safety report
- How do I install Infracost?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Infracost need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Infracost maintained?
- The last commit was 41 days ago (2026-09-24). The latest release is v1.0.1.
- How does Infracost compare with other MCP servers?
- safety score 94/100 (higher than 96% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.