Answer cloud spend questions with a billing MCP server
Ask an agent 'what drove last month's EC2 increase?' and it queries AWS billing data and explains the breakdown.
The use case
Engineering managers get asked why the cloud bill went up and have to dig through Cost Explorer filters. AWS Labs publishes MCP servers for Billing and Cost Management and for pricing, which let agents like Claude Code or Amazon Q query cost and usage data. An agent can break down spend by service, account or tag, compare months and point at the biggest changes. The manager still checks the numbers against the billing console before sharing, and decisions such as buying commitments or shutting resources down stay with people.
Example workflow
- Set up the billing MCP server with a read-only role
- Ask a question about a cost change
- Agent queries cost data and explains drivers
- Check key numbers in the billing console
- Decide actions with resource owners
Tools
- AWS Billing and Cost Management MCP Server
- AWS Cost Explorer
- Claude Code
Risks and guardrails
- Use read-only billing permissions
- Untagged resources skew breakdowns
- Never let the agent buy commitments or delete resources
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- AWS Labs: MCP servers: awslabs.github.io/mcp