AWS Cost Explorer

AWS Cost Explorer Overview

AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

This project provides an MCP (Model Control Protocol) server for analyzing AWS spend data, including Amazon Bedrock usage, through natural language queries using Anthropic's Claude Desktop or a LangGraph Agent. It integrates with AWS Cost Explorer and CloudWatch Logs to retrieve detailed cost and usage information.

How to Use AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

Prerequisites:

Python 3.12
AWS credentials with Cost Explorer access
Anthropic API access (for Claude integration)
(Optional) Amazon Bedrock access (for LangGraph Agent)
(Optional) Amazon EC2 for running a remote MCP server
Setup model invocation logs in Amazon CloudWatch.
Ensure IAM user/role has read-only access to Amazon Cost Explorer and Amazon CloudWatch.

Installation:

Install uv (package installer).
Clone the repository: git clone https://github.com/aarora79/aws-cost-explorer-mcp.git
Set up Python virtual environment and install dependencies: uv venv --python 3.12 && source .venv/bin/activate && uv pip install --requirement pyproject.toml
Configure AWS credentials in ~/.aws/credentials and ~/.aws/config.

Usage:

Local Setup: Run the server using export MCP_TRANSPORT=stdio && python server.py. Configure Claude Desktop by adding the provided JSON snippet to its configuration file, either using Docker or UV.
Remote Setup: Run the server on Amazon EC2 with export MCP_TRANSPORT=sse && python server.py. Configure an ingress rule for TCP port 8000. You can test with a CLI MCP client or a Chainlit app (chatbot) provided in the repository.
Secure Remote Setup: Use Nginx as a reverse proxy to provide an HTTPS endpoint for the MCP server. This involves configuring Nginx with SSL certificates and setting up appropriate security group rules.

Key Features of AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

Amazon EC2 Spend Analysis: Detailed breakdowns of EC2 spending.
Amazon Bedrock Spend Analysis: Breakdown by region, users, and models.
Service Spend Reports: Analyze spending across all AWS services.
Detailed Cost Breakdown: Granular cost data by day, region, service, and instance type.
Interactive Interface: Query cost data using natural language through Claude.
Cross-Account Access: Ability to get AWS spend information from other accounts by assuming roles.
Available Tools: Exposes tools like get_ec2_spend_last_day(), get_detailed_breakdown_by_day(), get_bedrock_daily_usage_stats(), and get_bedrock_hourly_usage_stats() for Claude to use.

Use Cases of AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

Cloud Cost Optimization: Understand and optimize AWS spend by identifying cost drivers.
Financial Reporting: Generate detailed reports on AWS expenditures.
Resource Management: Analyze spending patterns to better manage AWS resources.
AI-Powered Cost Analysis: Leverage natural language processing to interact with cost data, making it accessible to non-technical users.
Multi-Account Cost Management: Centralize cost analysis for multiple AWS accounts.

FAQ from AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

What is MCP? MCP (Model Control Protocol) is a framework by Anthropic that allows models like Claude to interact with external tools and services.
Can I analyze spend from multiple AWS accounts? Yes, the server supports cross-account access by configuring a CROSS_ACCOUNT_ROLE_NAME.
Does Claude Desktop support remote MCP servers? At this time, Claude Desktop does not directly support remote MCP servers. However, you can use a LangGraph Agent or a CLI client for remote interaction.
How can I secure my remote MCP server? You can use a reverse proxy like Nginx to provide an HTTPS endpoint for secure communication.
What kind of AWS data can I query? You can query EC2 spend, Bedrock usage, and general service spend across various dimensions like region, service, and instance type.
What are the available tools? The server exposes tools to get EC2 spend for the last day, detailed breakdowns by day, and daily/hourly Bedrock usage statistics.

AWS Cost Explorer's README

AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

An MCP server for getting AWS spend data via Cost Explorer and Amazon Bedrock usage data via Model invocation logs in Amazon Cloud Watch through Anthropic's MCP (Model Control Protocol). See section on "secure" remote MCP server to see how you can run your MCP server over HTTPS.

You can run the MCP server locally and access it via the Claude Desktop or you could also run a Remote MCP server on Amazon EC2 and access it via a MCP client built into a LangGraph Agent.

🚨You can also use this MCP server to get AWS spend information from other accounts as long as the IAM role used by the MCP server can assume roles in those other accounts🚨

Demo video

Overview

This tool provides a convenient way to analyze and visualize AWS cloud spending data using Anthropic's Claude model as an interactive interface. It functions as an MCP server that exposes AWS Cost Explorer API functionality to Claude Desktop, allowing you to ask questions about your AWS spend in natural language.

Features

Amazon EC2 Spend Analysis: View detailed breakdowns of EC2 spending for the last day
Amazon Bedrock Spend Analysis: View breakdown by region, users and models over the last 30 days
Service Spend Reports: Analyze spending across all AWS services for the last 30 days
Detailed Cost Breakdown: Get granular cost data by day, region, service, and instance type
Interactive Interface: Use Claude to query your cost data through natural language

Requirements

Python 3.12
AWS credentials with Cost Explorer access
Anthropic API access (for Claude integration)
[Optional] Amazon Bedrock access (for LangGraph Agent)
[Optional] Amazon EC2 for running a remote MCP server

Installation

Install uv:

# On macOS and Linux
curl -LsSf https://astral.sh/uv/install.sh | sh

# On Windows
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Additional installation options are documented here

Clone this repository: (assuming this will be updated to point to aws-samples?)

git clone https://github.com/aarora79/aws-cost-explorer-mcp.git
cd aws-cost-explorer-mcp

Set up the Python virtual environment and install dependencies:

uv venv --python 3.12 && source .venv/bin/activate && uv pip install --requirement pyproject.toml

Configure your AWS credentials:
```
mkdir -p ~/.aws
# Set up your credentials in ~/.aws/credentials and ~/.aws/config
```
If you useAWS IAM Identity Center, follow the docs to configure your short-term credentials

Usage

Prerequisites

Setup model invocation logs in Amazon CloudWatch.
Ensure that the IAM user/role being used has full read-only access to Amazon Cost Explorer and Amazon CloudWatch, this is required for the MCP server to retrieve data from these services. See here and here for sample policy examples that you can use & modify as per your requirements.
To allow your MCP server to access AWS spend information from other accounts set the the CROSS_ACCOUNT_ROLE_NAME parameter while starting the server and now you can provide the account AWS account id for another account while interacting with your agent and then agent will pass the account id to the server.

Local setup

Uses stdio as a transport for MCP, both the MCP server and client are running on your local machine.

Starting the Server (local)

Run the server using:

export MCP_TRANSPORT=stdio
export BEDROCK_LOG_GROUP_NAME=YOUR_BEDROCK_CW_LOG_GROUP_NAME
export CROSS_ACCOUNT_ROLE_NAME=ROLE_NAME_FOR_THE_ROLE_TO_ASSUME_IN_OTHER_ACCOUNTS # can be ignored if you do not want AWS spend info from other accounts
python server.py

Claude Desktop Configuration

There are two ways to configure this tool with Claude Desktop:

Option 1: Using Docker

Add the following to your Claude Desktop configuration file. The file can be found out these paths depending upon you operating system.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json.
Windows: %APPDATA%\Claude\claude_desktop_config.json.
Linux: ~/.config/Claude/claude_desktop_config.json.

{
  "mcpServers": {
    "aws-cost-explorer": {
      "command": "docker",
      "args": [ "run", "-i", "--rm", "-e", "AWS_ACCESS_KEY_ID", "-e", "AWS_SECRET_ACCESS_KEY", "-e", "AWS_REGION", "-e", "BEDROCK_LOG_GROUP_NAME", "-e", "MCP_TRANSPORT", "-e", "CROSS_ACCOUNT_ROLE_NAME", "aws-cost-explorer-mcp:latest" ],
      "env": {
        "AWS_ACCESS_KEY_ID": "YOUR_ACCESS_KEY_ID",
        "AWS_SECRET_ACCESS_KEY": "YOUR_SECRET_ACCESS_KEY",
        "AWS_REGION": "us-east-1",
        "BEDROCK_LOG_GROUP_NAME": "YOUR_CLOUDWATCH_BEDROCK_MODEL_INVOCATION_LOG_GROUP_NAME",
        "CROSS_ACCOUNT_ROLE_NAME": "ROLE_NAME_FOR_THE_ROLE_TO_ASSUME_IN_OTHER_ACCOUNTS",
        "MCP_TRANSPORT": "stdio"
      }
    }
  }
}

IMPORTANT: Replace YOUR_ACCESS_KEY_ID and YOUR_SECRET_ACCESS_KEY with your actual AWS credentials. Never commit actual credentials to version control.

Option 2: Using UV (without Docker)

If you prefer to run the server directly without Docker, you can use UV:

{
  "mcpServers": {
    "aws_cost_explorer": {
      "command": "uv",
      "args": [
          "--directory",
          "/path/to/aws-cost-explorer-mcp-server",
          "run",
          "server.py"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "YOUR_ACCESS_KEY_ID",
        "AWS_SECRET_ACCESS_KEY": "YOUR_SECRET_ACCESS_KEY",
        "AWS_REGION": "us-east-1",
        "BEDROCK_LOG_GROUP_NAME": "YOUR_CLOUDWATCH_BEDROCK_MODEL_INVOCATION_LOG_GROUP_NAME",
        "CROSS_ACCOUNT_ROLE_NAME": "ROLE_NAME_FOR_THE_ROLE_TO_ASSUME_IN_OTHER_ACCOUNTS",
        "MCP_TRANSPORT": "stdio"
      }
    }
  }
}

Make sure to replace the directory path with the actual path to your repository on your system.

Remote setup

Uses sse as a transport for MCP, the MCP servers on EC2 and the client is running on your local machine. Note that Claude Desktop does not support remote MCP servers at this time (see this GitHub issue).

Starting the Server (remote)

You can start a remote MCP server on Amazon EC2 by following the same instructions as above. Make sure to set the MCP_TRANSPORT as sse (server side events) as shown below. Note that the MCP uses JSON-RPC 2.0 as its wire format, therefore the protocol itself does not include authorization and authentication (see this GitHub issue), do not send or receive sensitive data over MCP.

Run the server using:

export MCP_TRANSPORT=sse
export BEDROCK_LOG_GROUP_NAME=YOUR_BEDROCK_CW_LOG_GROUP_NAME
export CROSS_ACCOUNT_ROLE_NAME=ROLE_NAME_FOR_THE_ROLE_TO_ASSUME_IN_OTHER_ACCOUNTS # can be ignored if you do not want AWS spend info from other accounts
python server.py

The MCP server will start listening on TCP port 8000.
Configure an ingress rule in the security group associated with your EC2 instance to allow access to TCP port 8000 from your local machine (where you are running the MCP client/LangGraph based app) to your EC2 instance.

Also see section on running a "secure" remote MCP server i.e. a server to which your MCP clients can connect over HTTPS.

Testing with a CLI MCP client

You can test your remote MCP server with the mcp_sse_client.py script. Running this script will print the list of tools available from the MCP server and an output for the get_bedrock_daily_usage_stats tool.

# set the hostname for your MCP server
MCP_SERVER_HOSTNAME=YOUR_MCP_SERVER_EC2_HOSTNAME
# or localhost if your MCP server is running locally
# MCP_SERVER_HOSTNAME=localhost 
AWS_ACCOUNT_ID=AWS_ACCOUNT_ID_TO_GET_INFO_ABOUT # if set to empty or if the --aws-account-id switch is not specified then it gets the info about the AWS account MCP server is running in
python mcp_sse_client.py --host $MCP_SERVER_HOSTNAME --aws-account-id $AWS_ACCOUNT_ID

Testing with Chainlit app

The app.py file in this repo provides a Chainlit app (chatbot) which creates a LangGraph agent that uses the LangChain MCP Adapter to import the tools provided by the MCP server as tools in a LangGraph Agent. The Agent is then able to use an LLM to respond to user questions and use the tools available to it as needed. Thus if the user asks a question such as "What was my Bedrock usage like in the last one week?" then the Agent will use the tools available to it via the remote MCP server to answer that question. We use Claude 3.5 Haiku model available via Amazon Bedrock to power this agent.

Run the Chainlit app using:

chainlit run app.py --port 8080

A browser window should open up on localhost:8080 and you should be able to use the chatbot to get details about your AWS spend.

Available Tools

The server exposes the following tools that Claude can use:

get_ec2_spend_last_day(): Retrieves EC2 spending data for the previous day
get_detailed_breakdown_by_day(days=7): Delivers a comprehensive analysis of costs by region, service, and instance type
get_bedrock_daily_usage_stats(days=7, region='us-east-1', log_group_name='BedrockModelInvocationLogGroup'): Delivers a per-day breakdown of model usage by region and users.
get_bedrock_hourly_usage_stats(days=7, region='us-east-1', log_group_name='BedrockModelInvocationLogGroup'): Delivers a per-day per-hour breakdown of model usage by region and users.

Example Queries

Once connected to Claude through an MCP-enabled interface, you can ask questions like:

"Help me understand my Bedrock spend over the last few weeks"
"What was my EC2 spend yesterday?"
"Show me my top 5 AWS services by cost for the last month"
"Analyze my spending by region for the past 14 days"
"Which instance types are costing me the most money?"
"Which services had the highest month-over-month cost increase?"

Docker Support

A Dockerfile is included for containerized deployment:

docker build -t aws-cost-explorer-mcp .
docker run -v ~/.aws:/root/.aws aws-cost-explorer-mcp

Development

Project Structure

server.py: Main server implementation with MCP tools
pyproject.toml: Project dependencies and metadata
Dockerfile: Container definition for deployments

Adding New Cost Analysis Tools

To extend the functionality:

Add new functions to server.py
Annotate them with @mcp.tool()
Implement the AWS Cost Explorer API calls
Format the results for easy readability

Secure "remote" MCP server

We can use nginx as a reverse-proxy so that it can provide an HTTPS endpoint for connecting to the MCP server. Remote MCP clients can connect to nginx over HTTPS and then it can proxy traffic internally to http://localhost:8000. The following steps describe how to do this.

Enable access to TCP port 443 from the IP address of your MCP client (your laptop, or anywhere) in the inbound rules in the security group associated with your EC2 instance.
You would need to have an HTTPS certificate and private key to proceed. Let's say you use your-mcp-server-domain-name.com as the domain for your MCP server then you will need an SSL cert for your-mcp-server-domain-name.com and it will be accessible to MCP clients as https://your-mcp-server-domain-name.com/sse. While you can use a self-signed cert but it would require disabling SSL verification on the MCP client, we DO NOT recommend you do that. If you are hosting your MCP server on EC2 then you could generate an SSL cert using no-ip or Let' Encrypt or other similar services. Place the SSL cert and private key files in /etc/ssl/certs and /etc/ssl/privatekey folders respectively on your EC2 machine.

Install nginx on your EC2 machine using the following commands.

sudo apt-get install nginx
sudo nginx -t
sudo systemctl reload nginx

Get the hostname for your EC2 instance, this would be needed for configuring the nginx reverse proxy.

TOKEN=$(curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600") && curl -H "X-aws-ec2-metadata-token: $TOKEN" -s http://169.254.169.254/latest/meta-data/public-hostname

Copy the following content into a new file /etc/nginx/conf.d/ec2.conf. Replace YOUR_EC2_HOSTNAME, /etc/ssl/certs/cert.pem and /etc/ssl/privatekey/privkey.pem with values appropriate for your setup.

server {
 listen 80;
 server_name YOUR_EC2_HOSTNAME;

 # Optional: Redirect HTTP to HTTPS
 return 301 https://$host$request_uri;
 }

 server {
     listen 443 ssl;
     server_name YOUR_EC2_HOSTNAME;

     # Self-signed certificate paths
     ssl_certificate     /etc/ssl/certs/cert.pem;
     ssl_certificate_key /etc/ssl/privatekey/privkey.pem; 

     # Optional: Good practice
     ssl_protocols       TLSv1.2 TLSv1.3;
     ssl_ciphers         HIGH:!aNULL:!MD5;

     location / {
         # Reverse proxy to your local app (e.g., port 8000)
         proxy_pass http://127.0.0.1:8000;
         proxy_http_version 1.1;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
     }
 }

Restart nginx.
```
sudo systemctl start nginx
```
Start your MCP server as usual as described in the remote setup section.
Your MCP server is now accessible over HTTPS as https://your-mcp-server-domain-name.com/sse to your MCP client.

On the client side now (say on your laptop or in your Agent) configure your MCP client to communicate to your MCP server as follows.

MCP_SERVER_HOSTNAME=YOUR_MCP_SERVER_DOMAIN_NAME
AWS_ACCOUNT_ID=AWS_ACCOUNT_ID_TO_GET_INFO_ABOUT # if set to empty or if the --aws-account-id switch is not specified then it gets the info about the AWS account MCP server is running in
python mcp_sse_client.py --host $MCP_SERVER_HOSTNAME --port 443 --aws-account-id $AWS_ACCOUNT_ID

Similarly you could run the chainlit app to talk to remote MCP server over HTTPS.

export MCP_SERVER_URL=YOUR_MCP_SERVER_DOMAIN_NAME
export MCP_SERVER_PORT=443
chainlit run app.py --port 8080

Similarly you could run the LangGraph Agent to talk to remote MCP server over HTTPS.

python langgraph_agent_mcp_sse_client.py --host $MCP_SERVER_HOSTNAME --port 443 --aws-account-id $AWS_ACCOUNT_ID

License

MIT License

Acknowledgments

This tool uses Anthropic's MCP framework
Powered by AWS Cost Explorer API
Built with FastMCP for server implementation
README was generated by providing a text dump of the repo via GitIngest to Claude

AWS Cost Explorer Reviews

Reviews feature coming soon

Stay tuned for community discussions and feedback

AWS Cost Explorer Overview

AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

How to Use AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

Key Features of AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

Use Cases of AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

FAQ from AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

AWS Cost Explorer's README

AWS Cost Explorer and Amazon Bedrock Model Invocation Logs MCP Server & Client

Demo video

Overview

Features

Requirements

Installation

Usage

Prerequisites

Local setup

Starting the Server (local)

Claude Desktop Configuration

Remote setup

Starting the Server (remote)

Testing with a CLI MCP client

Testing with Chainlit app

Available Tools

Example Queries

Docker Support

Development

Project Structure

Adding New Cost Analysis Tools

Secure "remote" MCP server

License

Acknowledgments

AWS Cost Explorer Reviews

Actions

AWS Cost Explorer's Information