Infracost MCP Server
Enables Claude to interact with Infracost for Terraform cost estimation and cloud governance. Supports generating cost breakdowns, comparing configurations, creating tagging policies, setting up cost guardrails, and posting cost comments to PRs.
README
Infracost MCP Server
MCP server that lets Claude interact with Infracost for Terraform cost estimation and cloud governance. Works with Claude Desktop and Claude Code.
What it does
- Generate cost breakdowns for Terraform configurations
- Compare costs between different configs or branches
- Create and manage tagging policies in Infracost Cloud
- Set up cost guardrails that block expensive PRs
- Post cost comments to GitHub/GitLab/Azure/Bitbucket PRs
- Upload custom properties for resource classification
Prerequisites
- Node.js >= 18
- Infracost CLI (for cost estimation tools)
- Infracost service token from Infracost Cloud > Org Settings > API tokens
Installation
git clone <repo-url> infracost_mcp
cd infracost_mcp
npm install
npm run build
Configuration
Create a .env file in the project root:
INFRACOST_SERVICE_TOKEN=ics_v1_your_token_here
INFRACOST_ORG=your_org_slug
Get your service token from the Infracost Cloud dashboard under Org Settings > API tokens.
Usage
With Claude Code
The repo includes .mcp.json and .claude/agents/ so it works out of the box - just open the project in Claude Code and the Infracost tools will be available.
With Claude Desktop
Add to your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"infracost": {
"command": "node",
"args": ["/absolute/path/to/infracost_mcp/dist/index.js"],
"env": {
"INFRACOST_SERVICE_TOKEN": "ics_v1_your_token"
}
}
}
}
Restart Claude Desktop after updating the config.
Examples
Natural Language Queries
Ask Claude things like:
Cost Estimation:
- "What's the monthly cost of my Terraform in ./infrastructure?"
- "Show me a cost breakdown for ./terraform/prod in table format"
- "Generate an HTML cost report and save it to report.html"
- "Upload the cost estimate from infracost.json to Infracost Cloud"
Cost Comparison:
- "Compare costs between ./staging and ./prod configs"
- "What's the cost difference if I switch from t3.medium to t3.large?"
- "Show me cost changes between the current branch and main"
Tagging Policies:
- "Create a tagging policy that requires Environment and Owner tags"
- "List all tagging policies for my organization"
- "Add a tagging policy that allows only 'dev', 'staging', 'prod' for Environment tags"
- "Update the tagging policy to also require a CostCenter tag"
Cost Guardrails:
- "Set up a guardrail that blocks PRs adding more than $200/month"
- "Create a guardrail that warns when total infrastructure cost exceeds $10k/month"
- "Block PRs with cost increases over 25% for my production repo"
- "List all active guardrails"
Pull Request Integration:
- "Post the cost estimate from infracost.json to GitHub PR #123 in owner/repo"
- "Add a cost comment to the current GitLab merge request"
JSON Examples
Generate cost breakdown:
{
"path": "./terraform/prod",
"format": "json",
"outFile": "cost-estimate.json"
}
Compare configurations:
{
"path": "./terraform/current",
"compareTo": "./terraform/baseline",
"format": "diff"
}
Create tagging policy:
{
"name": "Required tags policy",
"prComment": true,
"blockPr": true,
"tags": [
{
"key": "Environment",
"mandatory": true,
"valueType": "LIST",
"allowedValues": ["dev", "staging", "prod"]
},
{
"key": "Owner",
"mandatory": true,
"valueType": "REGEX",
"allowedRegex": "^[a-z]+\\.[a-z]+@company\\.com$"
}
]
}
Create cost guardrail:
{
"name": "Production cost limit",
"scope": {
"type": "REPO",
"repositories": ["myorg/prod-infrastructure"]
},
"increasePercentThreshold": 10,
"totalThreshold": 50000,
"blockPullRequest": true,
"commentOnPullRequest": true
}
See docs/EXAMPLES.md for more detailed examples.
Available Tools
CLI Tools (require Infracost CLI)
infracost_breakdown- Generate cost breakdown for Terraform infrastructureinfracost_diff- Show cost differences between two configurationsinfracost_output- Combine and format Infracost JSON filesinfracost_upload- Upload cost estimates to Infracost Cloudinfracost_comment- Post cost comments to pull requests
Cloud API Tools (require service token)
Tagging Policies:
infracost_cloud_list_tagging_policies- List all tagging policiesinfracost_cloud_get_tagging_policy- Get a specific tagging policyinfracost_cloud_create_tagging_policy- Create a new tagging policyinfracost_cloud_update_tagging_policy- Update an existing tagging policyinfracost_cloud_delete_tagging_policy- Delete a tagging policy
Guardrails:
infracost_cloud_list_guardrails- List all guardrailsinfracost_cloud_get_guardrail- Get a specific guardrailinfracost_cloud_create_guardrail- Create a cost guardrailinfracost_cloud_update_guardrail- Update an existing guardrailinfracost_cloud_delete_guardrail- Delete a guardrail
Custom Properties:
infracost_cloud_upload_custom_properties- Upload custom property values via CSV
Project Structure
src/- TypeScript source codedist/- Compiled JavaScript output (created bynpm run build)docs/- Additional documentation and examples.claude/- Claude Code agent configuration
Development
npm run build # Compile TypeScript
npm run watch # Watch mode for development
npm start # Run the MCP server
Troubleshooting
CLI tools not working:
- Verify Infracost CLI is installed:
infracost --version - Ensure
INFRACOST_SERVICE_TOKENis set correctly
Cloud API errors:
- Check that your service token has the necessary permissions
- Verify the organization slug is correct
Server not connecting:
- Ensure the path to
dist/index.jsis absolute in your MCP config - Restart Claude Desktop after making config changes
- Check that
npm run buildcompleted successfully
No resources found:
- Run
terraform initin your Terraform directory first - Verify the path to your Terraform files is correct
Resources
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.