MCP server for Infracost CLI integration - cloud cost estimates for Infrastructure as Code
MCP server for Infracost CLI integration - cloud cost estimates for Infrastructure as Code
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:
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| resourceTypes | ["aws_lambda_function", "aws_s3_bucket", "aws_dynamodb_table"] |
| outputFilePath | ./infracost-usage.json |
| includeGuidance | true |
| infracost_breakdown | |
| infracost_diff | |
| infracost_output | |
| infracost_comment | |
| infracost_upload | |
| infracost_configure | |
| infracost_auth | |
| infracost_generate_usage | Generates an Infracost usage file with sensible defaults for specified resource types. This is a utility tool that complements infracost_configure by providing pre-filled templates you can customize for your workloads. R |
{
"mcpServers": {
"infracost": {
"command": "npx",
"args": ["-y", "npm"],
"env": {
"INFRACOST_BINARY_PATH": "your-value",
"INFRACOST_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| INFRACOST_BINARY_PATH | Filesystem location the server is allowed to use. | Optional |
| INFRACOST_API_KEY | Credential the server authenticates with. | Yes |
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
kubectl with a conversational interface — inspect pods, read logs, diagnose clusters and manage workloads.