Infracost MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFRACOST_API_KEY | No | Infracost API key for cloud-backed features. | |
| INFRACOST_BINARY_PATH | No | Override path to Infracost binary. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| infracost_breakdownB | Generate cost breakdown for Infrastructure as Code (Terraform, CloudFormation, etc.). Shows cost estimates for cloud resources. |
| infracost_diffA | Show cost diff between current IaC and planned changes. Useful for pull request reviews to understand cost impact. |
| infracost_outputB | Format Infracost JSON output to different formats (table, html, github-comment, etc.). |
| infracost_commentA | Post cost estimate comments to pull requests on GitHub, GitLab, Azure Repos, or Bitbucket. |
| infracost_uploadA | Upload Infracost JSON output to Infracost Cloud for centralized cost visibility and reporting. |
| infracost_configureB | Get or set Infracost configuration options (API key, currency, etc.). |
| infracost_authA | Authenticate with Infracost Cloud. Opens browser for login flow. |
| infracost_generate_usageB | Generate Infracost usage file with sensible defaults for specified resource types. Complements infracost_configure by providing pre-filled templates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct action: breakdown (cost estimate), diff (comparison), output (formatting), comment (posting), upload (cloud sync), configure (settings), auth (login), and generate_usage (usage templates). There is no ambiguity between them.
All tools follow the consistent `infracost_<verb>` pattern, using snake_case throughout. Even though some verbs are nouns (output, breakdown), the prefix and lowercase snake_case make the set uniform and predictable.
Eight tools is a well-scoped count for a cost-estimation server, covering core operations without bloat. Each tool serves a clear purpose in the workflow.
The domain (Infracost cost analysis) is fully covered: generating estimates, diffs, formatted output, PR comments, cloud upload, authentication, configuration, and usage file generation. No obvious gaps exist for the intended purpose.