Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFRACOST_ORG | Yes | Your organization slug | |
| INFRACOST_SERVICE_TOKEN | Yes | Your Infracost service token (get from dashboard) |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| infracost_breakdown | Generate a cost breakdown for Terraform infrastructure. Analyzes Terraform configuration and provides detailed cost estimates for resources. Requires infracost CLI to be installed. |
| infracost_diff | Show cost differences between two Terraform configurations. Compares baseline and current infrastructure to identify cost changes. Requires infracost CLI to be installed. |
| infracost_output | Combine and format Infracost JSON files. Useful for merging multiple cost estimates or converting formats. Requires infracost CLI to be installed. |
| infracost_upload | Upload Infracost JSON output to Infracost Cloud for centralized cost tracking and reporting. Requires infracost CLI to be installed. |
| infracost_comment | Post cost estimate comments to pull requests on GitHub, GitLab, Azure Repos, or Bitbucket. Automatically updates existing comments. Requires infracost CLI to be installed and appropriate platform credentials. |
| infracost_cloud_list_tagging_policies | List all tagging policies in Infracost Cloud. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_get_tagging_policy | Get a specific tagging policy from Infracost Cloud. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_create_tagging_policy | Create a new tagging policy in Infracost Cloud for tag validation in pull requests. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_update_tagging_policy | Update tagging policies in Infracost Cloud with allowed tag values for validation in pull requests. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_delete_tagging_policy | Delete a tagging policy from Infracost Cloud. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_list_guardrails | List all guardrails in Infracost Cloud. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_get_guardrail | Get a specific guardrail from Infracost Cloud. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_create_guardrail | Create cost guardrails in Infracost Cloud that notify stakeholders or block PRs when cost thresholds are exceeded. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_update_guardrail | Update an existing guardrail in Infracost Cloud. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_delete_guardrail | Delete a guardrail from Infracost Cloud. Requires INFRACOST_SERVICE_TOKEN environment variable. |
| infracost_cloud_upload_custom_properties | Upload custom property values to Infracost Cloud via CSV for resource classification. Requires INFRACOST_SERVICE_TOKEN environment variable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Infracost Usage Defaults - Small ($5/month) | Small usage defaults for Infracost. Sets each usage-based cost to approximately $5/month for common configurations. Useful for development and small-scale environments. |
| Infracost Usage Defaults - Medium ($10/month) | Medium usage defaults for Infracost. Sets each usage-based cost to approximately $10/month for common configurations. Useful for staging and medium-scale environments. |
| Infracost Usage Defaults - Large ($20/month) | Large usage defaults for Infracost. Sets each usage-based cost to approximately $20/month for common configurations. Useful for production and large-scale environments. |
| Infracost Usage Example | Example infracost-usage.yml file showing how to customize usage values for specific resources. Can be used as a template for creating custom usage files. |