aws-billing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_CLI_BIN | No | The path to the AWS CLI executable. Defaults to 'aws'. | aws |
| AWS_PROFILE | No | The AWS CLI profile to use. Defaults to the system default profile. | |
| EXPECTED_ACCOUNT | No | Optional. If set, the server only allows access to this AWS account and rejects requests if the credentials do not match. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_cost_and_usageA | Query AWS cost and usage for account 135709585800 over a time period. Supports grouping (e.g. by SERVICE, USAGE_TYPE, REGION, LINKED_ACCOUNT, or a cost allocation TAG) and Cost Explorer filter expressions. Start date is inclusive, end date is exclusive. This is the primary tool for spend analysis: monthly trends, per-service breakdowns, daily spikes, etc. |
| get_dimension_valuesA | List available values for a Cost Explorer dimension in a time period — e.g. which services, regions, usage types, or linked accounts actually incurred cost. Use this to discover exact value strings before filtering in get_cost_and_usage. |
| get_cost_forecastA | Forecast future AWS spend for the account over a date range (must start today or later). Returns the mean forecast plus an 80% prediction interval. |
| get_cost_anomaliesA | List cost anomalies detected by AWS Cost Anomaly Detection in a date range, including root causes and impact. Returns an empty list if no anomaly monitors are configured. |
| describe_budgetsA | List AWS Budgets configured for the account, with limits, actual spend and forecast against each budget. |
| get_cost_allocation_tagsA | List cost allocation tag values seen in billing data for a time period. Provide tag_key to list its values; omit it to list available tag keys. Use these keys with group_by type=TAG in get_cost_and_usage. |
| get_commitment_utilizationA | Get Savings Plans or Reserved Instance utilization and coverage for a time period. Returns an explanatory message if the account has no such commitments. |
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 7 tools
Each tool serves a distinct purpose: querying cost/usage, discovering dimension values, forecasting, detecting anomalies, listing budgets, managing cost allocation tags, and checking commitment utilization. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case, using retrieval verbs like get_ and describe_. The pattern is uniform across the set, making it predictable for an agent.
With 7 tools, the server is well-scoped for its purpose of AWS billing and cost analysis. Each tool addresses a key aspect of cost management without being bloated or sparse.
The tool surface covers the core cost management workflows: historical analysis, forecasting, anomaly detection, budget tracking, tag discovery, and commitment utilization. There are no obvious dead ends or missing critical operations for a read-only billing server.