AWS DR Cost Estimator MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | The AWS region where Cost Explorer is available. Should be us-east-1. | us-east-1 |
| AWS_PROFILE | Yes | The AWS profile to use for Cost Explorer API access. | |
| FASTMCP_LOG_LEVEL | No | Log level for FastMCP server (e.g., DEBUG, INFO, WARNING). | WARNING |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dr_strategiesA | List the four supported DR strategies with labels and descriptions. |
| compare_dr_strategiesA | Compare DR cost across all four strategies using live Cost Explorer data. |
| analyze_dr_strategyA | Analyze DR cost for a single strategy using live Cost Explorer data. |
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 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.