AWS DR Cost Estimator MCP Server
OfficialProvides tools for estimating AWS disaster recovery costs by reading spending data from AWS Cost Explorer and applying strategy-specific multipliers for backup/restore, pilot light, warm standby, and active/active.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AWS DR Cost Estimator MCP Server Compare all four DR strategies for my AWS account over the last 6 months."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AWS DR Cost Estimator MCP Server
This sample is provided for demonstration and educational purposes only and is not intended for production use without additional security review and testing.
Plan your AWS disaster recovery (DR) budget conversationally. Ask your MCP-compatible assistant (Kiro, Cline, Claude, etc.) what it would cost to run DR under backup and restore, pilot light, warm standby, or active/active for your workload. Compare all four strategies side by side in one response.
The server reads your current spend from the AWS Cost Explorer API, applies DR cost multipliers derived from real customer engagements, and returns a budgetary estimate in seconds — with per-row confidence levels so you know where the estimate is well-grounded and where it needs further validation.
For the full methodology, see docs/methodology.md.
Quick start
1. Install
Add the server with one click.
Kiro | Cursor | VS Code |
Or paste this into your MCP client config manually:
{
"mcpServers": {
"dr-cost-estimator": {
"command": "uvx",
"args": ["--from", "git+https://github.com/aws-samples/sample-dr-cost-estimator-mcp.git", "dr-cost-estimator-mcp"],
"env": {
"FASTMCP_LOG_LEVEL": "WARNING",
"AWS_PROFILE": "your-aws-profile",
"AWS_REGION": "us-east-1"
}
}
}
}uvx fetches and runs the server from this repo with no clone or build needed.
2. Set up IAM permissions
Attach a policy granting ce:GetCostAndUsage to the IAM identity behind your AWS_PROFILE:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "DRCostEstimatorCostExplorerRead",
"Effect": "Allow",
"Action": "ce:GetCostAndUsage",
"Resource": "*",
"Condition": {
"StringEquals": {
"aws:RequestedRegion": "us-east-1"
}
}
}
]
}Cost Explorer doesn't support resource-level ARNs for GetCostAndUsage, so Resource must be *. The condition restricts calls to the us-east-1 endpoint (the only endpoint Cost Explorer uses). For additional controls, consider SCPs or aws:PrincipalTag conditions.
3. Ask your assistant
"Compare all four DR strategies for my AWS account over the last 6 months."That's it.
Related MCP server: AWS FinOps MCP Server
Example prompts
"Compare all four DR strategies for my AWS account over the last 6 months and show me estimated costs."
"Using my
prodAWS profile, analyze warm standby DR cost for the last 3 months.""For AWS accounts
111122223333and444455556666, analyze pilot light DR cost over the last 3 months.""Estimate DR costs for the workload tagged
Project=checkoutacross all my accounts.""Compare DR strategies for resources tagged
app=paymentsorapp=ledgerin production (env=prod).""What would warm standby cost if we keep 30% warm capacity?"
Features
Three tools:
list_dr_strategies,compare_dr_strategies,analyze_dr_strategyFour DR strategies: backup/restore, pilot light, warm standby, active/active
Live Cost Explorer input averaged over 1-24 complete months, optionally scoped by linked accounts or cost allocation tags
Usage-type-aware multipliers for RDS, OpenSearch, and Elastic Load Balancing (compute vs. storage vs. backup get separate multipliers)
Dollar-weighted confidence showing what fraction of spend has high-confidence vs. default-fallback multipliers
Per-row rationale with confidence level and plain-language explanation
Per-workload estimates via tags (
tag_filtersparameter)Tunable warm-standby capacity (0.1-1.0) to match your RTO requirements
For detailed parameters, response shapes, and example calls, see docs/tool_reference.md.
Customizing multipliers
The DR cost multipliers live in JSON files under dr_cost_estimator_mcp/core/data/; edit them directly in your clone. For a readable rendering of every shipped multiplier with its rationale, see docs/multiplier_reference.md (generated from the data files). For guidance on tuning multipliers for your portfolio, see docs/methodology.md.
Troubleshooting
Symptom | Fix |
Server doesn't appear in tool list | Restart your MCP client after config changes. Set |
| Check parameter ranges: |
| Verify |
Empty estimates (no error) | All line items matched the skip list (tax, refunds, support, Savings Plans). This is expected when there's no estimable spend. |
Numbers differ from Cost Explorer console | The tools use |
Security
The server is read-only: ce:GetCostAndUsage is the only AWS API call. It cannot create, modify, or delete any resource. No data is written to disk; all output goes to stderr.
Documentation
Methodology — multiplier tiers, assumptions, worked examples, customization guidance
Tool Reference — parameters, response shapes, example calls
Multiplier Reference — every shipped multiplier with rationale (generated)
License
This project is licensed under the MIT-0 License. See the LICENSE file for details.
Available Tools
3 toolsanalyze_dr_strategyA
Analyze DR cost for a single strategy using live Cost Explorer data.
Inputs: strategy (required), top_n, region, profile, +5 more. Returns: Response shape for the ``analyze_dr_strategy`` tool. Single-call deep-dive for…
compare_dr_strategiesA
Compare DR cost across all four strategies using live Cost Explorer data.
Inputs: top_n, region, profile, months_back, +4 more. Returns: Response shape for the ``compare_dr_strategies`` tool. Lightweight portfolio-wi…
list_dr_strategiesA
List the four supported DR strategies with labels and descriptions.
Inputs: no named parameters. Returns: Response shape for the ``list_dr_strategies`` tool.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a distinct purpose: listing strategies, comparing all strategies, and analyzing a single strategy. The scope difference between compare and analyze is clear, so there is minimal risk of misselection.
All tool names follow a verb_noun pattern with snake_case, using 'dr_strategy' as the core noun. The only variation is singular vs plural, which is semantically appropriate and does not break the overall consistency.
With 3 tools, the server is tightly scoped to its purpose of DR cost estimation. Each tool covers an essential operation (list, compare, analyze) without redundancy or unnecessary bloat.
The tool set covers the full read-only lifecycle of DR strategy costing: discovering available strategies, comparing all, and drilling into a single strategy. No obvious CRUD or analysis gaps exist for the stated purpose.
Maintenance
Related MCP Connectors
Ask about AWS, Azure, GCP, OpenAI, Anthropic and Snowflake costs, budgets, and anomalies.
FinOps assistant: query AWS, GCP and Azure cost, commitments, budgets and reports.
Create AWS cost estimates and shareable AWS Pricing Calculator URLs.
Cloud cost + FinOps knowledge for AI agents: AWS/Azure/GCP optimisation, AI spend, waste playbooks.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to analyze AWS costs, track spending trends, and detect anomalies directly within Claude Desktop using the AWS Cost Explorer API. It provides tools to identify major cost drivers and compare usage across different time periods through natural language queries.MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language analysis of AWS cloud costs, waste audits, and budget insights across multiple profiles and regions.MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language queries of AWS spend and Bedrock usage data, providing detailed breakdowns by service, region, account, user, instance type, and model, including cross-account cost analysis.-
- FlicenseNot gradedqualityAmaintenanceEnables users to query and analyze AWS cloud spending and Amazon Bedrock model usage through natural language, with breakdowns by day, region, service, instance type, user, and model, including cross-account cost visibility.-