MCP server for Infracost CLI integration - cloud cost estimates for Infrastructure as Code
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-downatthebottomofthemolehole-infracost": {
"args": [
"-y",
"npm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Note: This is a community-maintained MCP server. It is not an official Model Context Protocol server from Infracost.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / finance
MCP server for using the GitLab API
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
MCP Security Weekly
Get CVE alerts and security updates for io.github.DownAtTheBottomOfTheMoleHole/infracost and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.

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.
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.infracost_generate_usage to generate usage files with sensible defaults.This MCP server is platform-agnostic and works in local and CI environments:
The primary requirements are Node.js and the Infracost CLI binary.
| Tool | Category | Typical outcome |
|---|---|---|
infracost_breakdown | Estimation | Monthly cost baseline for current IaC |
infracost_diff | Comparison | Cost delta from a planned change |
infracost_output | Reporting | Rendered table/JSON/HTML/comment output |
infracost_comment | Collaboration | PR comment with estimated impact |
infracost_upload | Cloud Sync | Cost report visible in Infracost Cloud |
infracost_configure | Configuration | Persisted CLI config update/read |
infracost_auth | Authentication | Login flow for Infracost Cloud |
infracost_generate_usage | Utilities | Pre-filled usage file template with defaults |
infracost_breakdownRuns 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.extraArgs (string[], optional): Additional CLI arguments.infracost_diffRuns infracost diff.
Inputs:
workingDirectory (string, optional): Command working directory.path (string, optional): Path to Terraform/IaC dire