This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: superceeded by awslabs.aws-pricing-mcp-server
Cost Analysis MCP Server
MCP server for analyzing AWS service costs and generating cost reports
Features
Analyze and visualize AWS costs
- Get detailed breakdown of your AWS costs by service, region and tier
- Understand how costs are distributed across various services
Query cost data with natural language
- Ask questions about your AWS costs in plain English, no complex query languages required
- Get instant answers fetched from pricing webpage and AWS Pricing API, for questions related to AWS services
Generate cost reports and insights
- Generate comprehensive cost reports based on your IaC implementation
- Get cost optimization recommendations
Prerequisites
- Install
uvfrom Astral or the GitHub README - Install Python using
uv python install 3.10 - Set up AWS credentials with access to AWS services
- You need an AWS account with appropriate permissions
- Configure AWS credentials with
aws configureor environment variables - Ensure your IAM role/user has permissions to access AWS Pricing API
Installation
Here are some ways you can work with MCP across AWS, and we'll be adding support to more products including Amazon Q Developer CLI soon: (e.g. for Amazon Q Developer CLI MCP, ~/.aws/amazonq/mcp.json):
{
"mcpServers": {
"awslabs.cost-analysis-mcp-server": {
"command": "uvx",
"args": ["awslabs.cost-analysis-mcp-server@latest"],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR",
"AWS_PROFILE": "your-aws-profile"
},
"disabled": false,
"autoApprove": []
}
}
}
AWS Authentication
The MCP server uses the AWS profile specified in the AWS_PROFILE environment variable. If not provided, it defaults to the "default" profile in your AWS configuration file.
"env": {
"AWS_PROFILE": "your-aws-profile"
}
Make sure the AWS profile has permissions to access the AWS Pricing API. The MCP server creates a boto3 session using the specified profile to authenticate with AWS services. Your AWS IAM credentials remain on your local machine and are strictly used for accessing AWS services.
2 maintainers
Release files for awslabs.cost-analysis-mcp-server 0.0.2025141004
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| awslabs_cost_analysis_mcp_server-0.0.2025141004.tar.gz | 69.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awslabs_cost_analysis_mcp_server-0.0.2025141004-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:111.4 kB
Release files / awslabs_cost_analysis_mcp_server-0.0.2025141004.tar.gz
| Download URL | awslabs_cost_analysis_mcp_server-0.0.2025141004.tar.gz |
|---|---|
| Size | 69.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ff8f2473cc49425bc1a220f9d39bb95a30d5044f9f3563cb73b00d9210b969a
|
|
BLAKE2b-256 checksum How to use checksums |
a367cf61f2453cb6bd1d3d7cc2c410f662908658473e418f6fa8d5588beec088
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2025.
Transparency logRelease files / awslabs_cost_analysis_mcp_server-0.0.2025141004-py3-none-any.whl
| Download URL | awslabs_cost_analysis_mcp_server-0.0.2025141004-py3-none-any.whl |
|---|---|
| Size | 41.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a3c74e3add24daf0aebdff828352276bf4646b9220fea248305b8a82b37df8a7
|
|
BLAKE2b-256 checksum How to use checksums |
64b2da1b0ea17b9f2fcc93c08d4f004256670a5ef496398fe9f31ffe1f9b3a39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2025.
Transparency log
