Back to catalog
A

Official Vendor Server

Amazon Web Services✦ Lab Verified

AWS Billing

Comprehensive AWS billing and cost management. Budgets, anomaly detection, free tier usage, pricing calculator, and optimization recommendations.

9.1/10

Score

704ms

Latency

Local

Uptime

25

Tools

stdio

Auth

Officialvendor-verifiedsecurity-scannedinfrastructurefinance

Ecosystem

Amazon Web Services MCP Servers

8 specialized servers, 85 tools tested independently. Each link leads to a full review with tool-level evidence.

ServerScoreSecurity
AWS Documentation94/1009/10
AWS IAM94/1009/10
AWS93/1009/10
AWS Cost Explorer92/1009/10
AWS Well-Architected Security92/1009/10
AWS Pricing91/1008/10
AWS CloudTrail90/1008/10
AWS CloudWatch90/1008/10
25 discovered12 executed12 success
Median latency: 704ms

Quick Verdict

Use this for AWS cost analysis and budget monitoring. Avoid it for real-time cost alerts due to 1905ms peak latency. Best area: billing data access across 12 tools. Biggest failure: none in current tests.

Lab Review

What We Found

What works: AWS Billing's MCP server delivers cost analysis without surprises. Our tests covered 12 tools spanning cost explorer, pricing data, budgets and compute optimizer - all executed cleanly. The cost-explorer and aws-pricing tools return detailed JSON structures that give you exactly the billing breakdowns you need for cost monitoring dashboards. Where it breaks: Latency is the main pain point we hit during testing. Several tools pushed past 1900ms response times, particularly session-sql which lets you query billing data directly. The server supports local stdio transport and our tests used API key credentials, but those slow responses will frustrate interactive cost analysis sessions where you're exploring spending patterns in real-time. What this means for your workflow: All 12 tested tools performed reliably, so you can build automated cost reporting on any of these endpoints. The budgets and cost-anomaly tools are solid choices for scheduled reports where latency doesn't matter. Avoid building interactive cost exploration features that depend on sub-second responses - the current performance makes real-time cost drilling a poor user experience. For automated billing workflows, this server is ready. For interactive cost analysis, the delays will frustrate users.

Lab Observations

What actually happened during testing

During testing, our scanner interacted with AWS Billing. 12 tools succeeded.

ToolStatus
cost-explorer success
aws-pricing success
budgets success
cost-anomaly success
free-tier-usage success
compute-optimizer success
list-billing-groups success
list-account-associations success
list-custom-line-items success
list-pricing-rules success
list-pricing-plans success
session-sql success

Reliability

10/10

Partial runtime test — 12 of 25 tools executed Score based on transport stability and schema completeness.

Score Breakdown

10/10

Reliability

12 of 12 executed tools succeeded.

8/10

Security

Score based on schema analysis and dependency audit.

9/10

Setup

Local stdio server. Install via npx or binary, no auth required.

8.9/10

Docs

25 tools with descriptions and input schemas.

10/10

Compatibility

Standard MCP protocol. Transport: stdio.

9.4/10

Maintenance

Based on commit frequency, releases, and contributor activity.

Tools

25 available tools

cost-explorer

Retrieves AWS cost and usage data using the Cost Explorer API. IMPORTANT USAGE GUIDELINES: - Use UnblendedCost metric by default (not BlendedCost) unless user specifies otherwise - Exclude record_types 'Credit' and 'Refund' by default unless user requests inclusion - Choose DAILY granularity for periods <3 months, MONTHLY for longer periods - Start with high-level dimensions (SERVICE, LINKED_ACCOUNT) before detailed ones - Always remember that the end_date is exclusive USE THIS TOOL FOR: - **Historical cost trends** and spending analysis (any time period) - **Usage pattern analysis** over time - **Cost breakdown** by service, account, region, or any dimension - **Forecasting** future costs and usage - **Resource-level cost analysis** (last 14 days) - **Multi-dimensional cost analysis** with complex grouping ## OPERATIONS 1) getCostAndUsage — account-level historical cost/usage Required: operation="getCostAndUsage", start_date, end_date, granularity, metrics Optional: group_by, filter, next_token, max_pages Example: {"operation": "getCostAndUsage", "start_date": "2024-01-01", "end_date": "2024-02-01", "granularity": "DAILY", "metrics": ["UnblendedCost"], "group_by": "[{"Type": "DIMENSION", "Key": "SERVICE"}]"} 2. getCostAndUsageWithResources - Resource-level cost data (limited to last 14 days) Required: operation="getCostAndUsageWithResources", filter, granularity, start_date, end_date Optional: metrics, group_by Notes: RESOURCE_ID must be included in either filter OR group_by parameters. This operation is limited to past 14 days of data from current date. Hourly granularity is only available for EC2-Instances resource-level data. All other resource-level data is available at daily granularity. Example: {"operation": "getCostAndUsageWithResources", "start_date": "2025-08-07", "end_date": "2025-08-21", "granularity": "DAILY", "filter": "{"Dimensions": {"Key": "SERVICE", "Values": ["Amazon Elastic Compute Cloud - Compute"]}}", "group_by": "[{"Type": "DIMENSION", "Key": "RESOURCE_ID"}]"} Returns: Cost data with resource-level granularity 3. getDimensionValues - List of available values for specified dimension Required: operation="getDimensionValues", dimension, start_date, end_date Optional: context, search_string, filter, max_results Example: {"operation": "getDimensionValues", "dimension": "SERVICE", "start_date": "2024-01-01", "end_date": "2024-02-01"} Returns: List of values for specified dimension with automatic pagination 4. getCostForecast - Future cost projections Required: operation="getCostForecast", metric, granularity, start_date, end_date Optional: filter, prediction_interval_level Example: {"operation": "getCostForecast", "metric": "UNBLENDED_COST", "granularity": "MONTHLY", "start_date": "2025-08-22", "end_date": "2025-11-22"} Notes: metric value for this operation should be in all caps Returns: Cost forecast for specified time period and granularity 5. getUsageForecast - Future usage projections Required: operation="getUsageForecast", metric, granularity, start_date, end_date, filter Optional: prediction_interval_level Example 1: {"operation": "getUsageForecast", "metric": "USAGE_QUANTITY", "granularity": "MONTHLY", "start_date": "2025-08-22", "end_date": "2025-11-22", "filter": "{"Dimensions": {"Key": "USAGE_TYPE_GROUP", "Values": ["EC2-Instance"]}}"} Example 2: {"operation": "getUsageForecast", "metric": "USAGE_QUANTITY", "granularity": "MONTHLY", "start_date": "2025-08-22", "end_date": "2025-11-22", "filter": "{"And": [{"Dimensions": {"Key": "SERVICE", "Values": ["Amazon Elastic Compute Cloud - Compute"]}}, {"Dimensions": {"Key": "USAGE_TYPE", "Values": ["BoxUsage:p4de.24xlarge"]}}]}"} Example 3: {"operation": "getUsageForecast", "metric": "USAGE_QUANTITY", "granularity": "MONTHLY", "start_date": "2025-08-22", "end_date": "2025-11-22", "filter": "{"Dimensions": {"Key": "USAGE_TYPE", "Values": ["BoxUsage:p4de.24xlarge", "Reservation:p4de.24xlarge", "UnusedBox:p4de.24xlarge"]}}", "group_by": "[{"Type": "DIMENSION", "Key": "REGION"}]"} Notes: Valid values for metric is: USAGE_QUANTITY, NORMALIZED_USAGE_AMOUNT. Valid values for granularity is: DAILY, MONTHLY. Filter is REQUIRED and must specify USAGE_TYPE or USAGE_TYPE_GROUP to define what usage units to forecast. Returns: Usage forecast for specified time period and granularity 6. getTagsOrValues - Available cost allocation tags or values Required: operation="getTagsOrValues" Optional: start_date, end_date, search_string, next_token, max_pages Example 1: {"operation": "getTagsOrValues"} Example 2: {"operation": "getTagsOrValues", "tag_key": "Environment"} Returns: List of available cost allocation tags with automatic pagination. If tag values for a particular key are needed, pass the tag key as a parameter. 8. getCostCategories - Available cost categories Required: operation="getCostCategories", start_date, end_date Optional: search_string, next_token, max_pages Example: {"operation": "getCostCategories", "start_date": "2024-01-01", "end_date": "2024-08-01"} Returns: List of available cost categories with automatic pagination 9. getSavingsPlansUtilization - Savings Plans utilization data Required: operation="getSavingsPlansUtilization", start_date, end_date Optional: granularity, filter Example: {"operation": "getSavingsPlansUtilization", "granularity": "MONTHLY"} Notes: This operation supports only DAILY and MONTHLY granularity Returns: Savings Plans utilization for the specified time period DIMENSION REFERENCE: - AZ: The Availability Zone (e.g., us-east-1a) - DATABASE_ENGINE: The Amazon RDS database (e.g., Aurora, MySQL) - DEPLOYMENT_OPTION: RDS deployment scope (SingleAZ, MultiAZ) - INSTANCE_TYPE: The EC2 instance type (e.g., m4.xlarge) - INSTANCE_TYPE_FAMILY: Family of instances (e.g., Compute Optimized, Memory Optimized) - LINKED_ACCOUNT: AWS member accounts - OPERATING_SYSTEM: OS type (e.g., Windows, Linux) - PLATFORM: EC2 operating system - PURCHASE_TYPE: Reservation type (e.g., On-Demand, Reserved) - REGION: AWS Region - SERVICE: AWS service (e.g., Amazon DynamoDB) - TAG: Cost allocation tag - TENANCY: EC2 tenancy (shared, dedicated) - USAGE_TYPE: Usage type (e.g., DataTransfer-In-Bytes) - RECORD_TYPE: Charge types (e.g., RI fees, usage costs)

compute-optimizer

Retrieves recommendations from AWS Compute Optimizer. IMPORTANT USAGE GUIDELINES: - Focus on recommendations with the highest estimated savings first - Include all relevant details when presenting specific recommendations USE THIS TOOL FOR: - **Performance optimization** (CPU, memory, network utilization analysis) - **Performance-based rightsizing** (not cost-based) DO NOT USE FOR: Cost optimization or idle detection (use cost-optimization-hub) This tool supports the following operations: 1. get_ec2_instance_recommendations: Get recommendations for EC2 instances 2. get_auto_scaling_group_recommendations: Get recommendations for Auto Scaling groups 3. get_ebs_volume_recommendations: Get recommendations for EBS volumes 4. get_lambda_function_recommendations: Get recommendations for Lambda functions 5. get_rds_recommendations: Get recommendations for RDS instances 6. get_ecs_service_recommendations: Get recommendations for ECS services Each operation can be filtered by AWS account IDs, regions, finding types, and more. Common finding types include: - UNDERPROVISIONED: The resource doesn't have enough capacity - OVERPROVISIONED: The resource has excess capacity and could be downsized - OPTIMIZED: The resource is already optimized - NOT_OPTIMIZED: The resource can be optimized but specific finding type isn't available

cost-optimization

Retrieves cost optimization recommendations from AWS Cost Optimization Hub. IMPORTANT USAGE GUIDELINES: - Focus on recommendations with the highest estimated savings first - Include all relevant details when presenting specific recommendations USE THIS TOOL FOR: - **Idle/unused resource detection** (EC2, RDS, EBS, Lambda, etc.) - **Cost savings recommendations** (rightsizing, stopping, deleting resources) - **Reserved Instance and Savings Plans purchase recommendations** - **Cross-service cost optimization analysis** - **Monthly cost reduction opportunities** DO NOT USE FOR: Performance optimization (use compute-optimizer) Supported Operations: 1. list_recommendation_summaries: High-level overview of savings opportunities grouped by a dimension 2. list_recommendations: Detailed list of specific recommendations 3. get_recommendation: Get detailed information about a specific recommendation IMPORTANT: 'list_recommendation_summaries' operation REQUIRES a 'group_by' parameter. Valid 'group_by' values: AccountId, Region, ActionType, ResourceType, RestartNeeded, RollbackPossible, ImplementationEffort CRITICAL PARAMETER REQUIREMENTS: - 'filters' parameter must be passed as JSON string format - 'max_results' must be integer (not string) - 'get_recommendation' requires both 'resource_id' AND 'resource_type' parameters - Service only available in us-east-1 region Available Filter Parameters (pass as JSON string): - resourceTypes: ['Ec2Instance', 'LambdaFunction', 'EbsVolume', 'EcsService', 'Ec2AutoScalingGroup', 'Ec2InstanceSavingsPlans', 'ComputeSavingsPlans', 'SageMakerSavingsPlans', 'Ec2ReservedInstances', 'RdsReservedInstances', 'OpenSearchReservedInstances', 'RedshiftReservedInstances', 'ElastiCacheReservedInstances', 'RdsDbInstanceStorage', 'RdsDbInstance', 'DynamoDbReservedCapacity', 'MemoryDbReservedInstances'] - actionTypes: ['Rightsize', 'Stop', 'Upgrade', 'PurchaseSavingsPlans', 'PurchaseReservedInstances', 'MigrateToGraviton', 'Delete', 'ScaleIn'] - implementationEfforts: ['VeryLow', 'Low', 'Medium', 'High', 'VeryHigh'] - regions: AWS region codes (e.g., ["us-east-1", "us-west-2"]) - accountIds: List of AWS account IDs - restartNeeded: boolean - rollbackPossible: boolean Cost Optimization Hub provides recommendations across multiple AWS services, including: - EC2 instances (right-sizing, Graviton migration) - EBS volumes (unused volumes, IOPS optimization) - RDS instances (right-sizing, engine optimization) - Lambda functions (memory size optimization) - SP/RI - And more Each recommendation includes: - The resource ARN and ID - The estimated monthly savings - The current state of the resource - The recommended state of the resource

storage-lens

Query S3 Storage Lens metrics data using Athena SQL. IMPORTANT USAGE GUIDELINES: - Before using this tool, provide a 1-3 sentence explanation starting with "EXPLANATION:" - Use standard SQL syntax for Athena queries - Use {table} as a placeholder for the Storage Lens metrics table name - Perform aggregations (GROUP BY) when analyzing data across multiple dimensions This tool allows you to analyze S3 Storage Lens metrics data using SQL queries. Storage Lens provides metrics about your S3 storage, including: - Storage metrics: Total bytes, object counts by storage class - Cost optimization metrics: Transition opportunities, incomplete multipart uploads - Data protection metrics: Replication, versioning, encryption status - Activity metrics: Upload, download, and request metrics STORAGE LENS EXPORT SCHEMA: The Storage Lens export data has the following standard columns: - version_number: The version of the S3 Storage Lens metrics being used - configuration_id: The configuration_id of your S3 Storage Lens configuration - report_date: The date that the metrics were tracked - aws_account_number: Your AWS account number - aws_region: The AWS Region for which the metrics are being tracked - storage_class: The storage class (STANDARD, STANDARD_IA, GLACIER, etc.) - record_type: The type of artifact being reported (ACCOUNT, BUCKET, PREFIX, STORAGE_LENS_GROUP_BUCKET, STORAGE_LENS_GROUP_ACCOUNT) - record_value: The value of the record_type artifact (account ID, bucket name, prefix, or Storage Lens group ARN) - bucket_name: The name of the bucket (when record_type is BUCKET or PREFIX) - metric_name: The name of the metric (e.g., 'StorageBytes', 'ObjectCount', 'EncryptedStorageBytes') - metric_value: The numeric value of the metric IMPORTANT: Metrics are stored in rows, not columns. Each row represents one metric value for a specific combination of dimensions. Environment variables: - STORAGE_LENS_MANIFEST_LOCATION: S3 URI to manifest file or folder (required) - STORAGE_LENS_OUTPUT_LOCATION: S3 location for Athena query results (optional) Example queries: 1. Top 10 buckets by storage size: SELECT bucket_name, SUM(CAST(metric_value AS BIGINT)) as total_size FROM {table} WHERE metric_name = 'StorageBytes' GROUP BY bucket_name ORDER BY total_size DESC LIMIT 10 2. Storage distribution by storage class: SELECT storage_class, SUM(CAST(metric_value AS BIGINT)) as total_size FROM {table} WHERE metric_name = 'StorageBytes' GROUP BY storage_class ORDER BY total_size DESC 3. Buckets with incomplete multipart uploads: SELECT bucket_name, SUM(CAST(metric_value AS BIGINT)) as incomplete_bytes FROM {table} WHERE metric_name = 'IncompleteMultipartUploadStorageBytes' AND CAST(metric_value AS BIGINT) > 0 GROUP BY bucket_name ORDER BY incomplete_bytes DESC 4. Storage Distribution by Region and Storage Class: SELECT aws_region, storage_class, SUM(CAST(metric_value AS BIGINT)) as total_bytes FROM {table} WHERE metric_name = 'StorageBytes' GROUP BY aws_region, storage_class ORDER BY total_bytes DESC 5. Object Lifecycle Management Opportunities: SELECT aws_region, storage_class, SUM(CASE WHEN metric_name = 'NonCurrentVersionStorageBytes' THEN CAST(metric_value AS BIGINT) ELSE 0 END) as noncurrent_bytes, SUM(CASE WHEN metric_name = 'StorageBytes' THEN CAST(metric_value AS BIGINT) ELSE 0 END) as total_bytes FROM {table} WHERE metric_name IN ('NonCurrentVersionStorageBytes', 'StorageBytes') GROUP BY aws_region, storage_class HAVING SUM(CASE WHEN metric_name = 'NonCurrentVersionStorageBytes' THEN CAST(metric_value AS BIGINT) ELSE 0 END) > 0 ORDER BY noncurrent_bytes DESC 6. Lifecycle Rule Analysis: SELECT bucket_name, SUM(CASE WHEN metric_name = 'TotalLifecycleRuleCount' THEN CAST(metric_value AS INTEGER) ELSE 0 END) as lifecycle_rule_count, SUM(CASE WHEN metric_name = 'StorageBytes' THEN CAST(metric_value AS BIGINT) ELSE 0 END) as total_bytes FROM {table} WHERE metric_name IN ('TotalLifecycleRuleCount', 'StorageBytes') GROUP BY bucket_name ORDER BY lifecycle_rule_count ASC, total_bytes DESC

aws-pricing

Comprehensive AWS pricing analysis tool that provides access to AWS service pricing information and cost analysis capabilities. This tool supports four main operations: 1. get_service_codes: Get a comprehensive list of AWS service codes from the AWS Price List API 2. get_service_attributes: Get filterable attributes for a specific AWS service's pricing 3. get_attribute_values: Get all valid values for a specific attribute of an AWS service 4. get_pricing_from_api: Get detailed pricing information from AWS Price List API with optional filters USE THE OPERATIONS IN THIS ORDER: 1. get_service_codes: Entry point - discover available AWS services and their unique service codes. Note that service codes may not match your expectations, so it's best to get service codes first. 2. get_service_attributes: Second step - understand which dimensions affect pricing for a chosen service 3. get_attribute_values: Third step - get possible values you can use in pricing filters 4. get_pricing_from_api: Final step - retrieve actual pricing data based on service and filters **If you deviate from this order of operations, you will struggle to form the correct filters, and you will not get results from the API** IMPORTANT GUIDELINES: - When retrieving foundation model pricing, always use the latest models for comparison - For database compatibility with services, only include confirmed supported databases - Providing less information is better than giving incorrect information - Price list APIs can return large data volumes. Use narrower filters to retrieve less data when possible - Service codes often differ from AWS console names (e.g., 'AmazonES' for OpenSearch) ARGS: ctx: The MCP context object operation: The pricing operation to perform ('get_service_codes', 'get_service_attributes', 'get_attribute_values', 'get_pricing_from_api') service_code: AWS service code (e.g., 'AmazonEC2', 'AmazonS3', 'AmazonES'). Required for get_service_attributes, get_attribute_values, and get_pricing_from_api operations. attribute_name: Attribute name (e.g., 'instanceType', 'location', 'storageClass'). Required for get_attribute_values operation. region: AWS region (e.g., 'us-east-1', 'us-west-2', 'eu-west-1'). Required for get_pricing_from_api operation. filters: Optional filters for pricing queries. Format: {'instanceType': 't3.medium', 'location': 'US East (N. Virginia)'} RETURNS: Dict containing the pricing information SUPPORTED AWS PRICING API REGIONS: - Classic partition: us-east-1, eu-central-1, ap-southeast-1 - China partition: cn-northwest-1 The tool automatically maps your region to the nearest pricing endpoint.

Show all 25 tools →
bcm-pricing-calc

Allows working with workload estimates using the AWS Billing and Cost Management Pricing Calculator API. IMPORTANT USAGE GUIDELINES: - Always first check the rate preference setting for the authorized principal by calling the get_preferences operation. - DO NOT state assumptions about Free Tier API USE THIS TOOL FOR: - Listing available **workload estimates** for the logged in account. - **Filter list of available workload estimates** using name, status, created date, or expiration date. - Get **details of a workload estimate**. - Get the list of **services, usage type, operation, and usage amount** modeled within a workload estimate. - Get **rate preferences** set for Pricing Calculator. These rate preferences denote what rate preferences can be used by each account type in your organization. ## OPERATIONS 1) list_workload_estimates - list of available workload estimates Required: operation="list_workload_estimates" Optional: created_after, created_before, expires_after, expires_before, status_filter, name_filter, name_match_option, next_token, max_results Returns: List of all workload estimates for the account. 2) get_workload_estimate - get details of a workload estimate Required: operation="get_workload_estimate", identifier Returns: Details of a specific workload estimate. 3) list_workload_estimate_usage - list of modeled usage lines within a workload estimate Required: operation="get_workload_estimate", identifier Optional: usage_account_id_filter, service_code_filter, usage_type_filter, operation_filter, location_filter, usage_group_filter, next_token, max_results Returns: List of usage associated with a workload estimate. 4) get_preferences - get the rate preferences available to an account Required: operation="get_preferences" Returns: Retrieves the current preferences for AWS Billing and Cost Management Pricing Calculator.

budgets

Retrieves AWS budget information using the AWS Budgets API. This tool uses the DescribeBudgets API to retrieve all budgets for an account. The API returns information about: - Budget names, types, and time periods - Budget limits (amount and unit) - Current actual spend - Forecasted spend - Cost filters applied to budgets With this information, you can determine which budgets have been exceeded or are projected to exceed their limits. The tool automatically retrieves the AWS account ID of the calling identity or uses the provided account_id.

cost-anomaly

Retrieves AWS cost anomalies using the Cost Explorer GetAnomalies API. This tool allows you to retrieve cost anomalies detected on your AWS account during a specified time period. Anomalies are available for up to 90 days. You can filter anomalies by: - Date range (required) - Monitor ARN (optional) - Feedback status (optional) - Total impact (optional) Feedback status options: - YES: Anomalies marked as accurate - NO: Anomalies marked as inaccurate - PLANNED_ACTIVITY: Anomalies marked as planned activities

cost-comparison

Retrieves AWS cost comparisons between two one-month periods. Do not use this tool except for comparing the costs of one month to the costs of another month. This tool should not be used for week-over-week or quarter-over-quarter (e.g., comparing Q2 vs. Q1) analysis. USE THIS TOOL ONLY FOR: - **Month-to-month cost variance analysis** (e.g., January vs February) - **Root cause analysis** of cost changes between specific months - **Detailed cost driver identification** (what exactly caused the cost change) - **Service-level impact analysis** for month-over-month changes - **Executive reporting** on monthly cost variances STRICT LIMITATIONS: - ONLY compares exactly one month to another month - Both periods must start on 1st day of month, end on 1st day of next month - Cannot compare weeks, quarters, or custom periods - DO NOT USE for general cost analysis or flexible time periods This tool supports two main operations: 1. getCostAndUsageComparisons: Compare costs between two time periods with flexible grouping and filtering 2. getCostComparisonDrivers: Identify key factors driving cost changes between two time periods Both operations require: - BaselineTimePeriod: Earlier time period for comparison (must be exactly one month) - ComparisonTimePeriod: Later time period for comparison (must be exactly one month) - MetricForComparison: The cost metric to compare (e.g., BlendedCost, UnblendedCost) Supported metrics for comparison include: - AmortizedCost: Costs with upfront and recurring reservation fees spread across the period - BlendedCost: Average cost of all usage throughout the billing period - NetAmortizedCost: Amortized cost after discounts - NetUnblendedCost: Unblended cost after discounts - NormalizedUsageAmount: Normalized usage amount - UnblendedCost: Actual costs incurred during the specified period - UsageQuantity: Usage amounts in their respective units You can group results by dimensions such as: - SERVICE: AWS service (e.g., Amazon EC2, Amazon S3) - LINKED_ACCOUNT: Member accounts in an organization - REGION: AWS Region - USAGE_TYPE: Type of usage (e.g., BoxUsage:t2.micro) - INSTANCE_TYPE: EC2 instance type (e.g., t2.micro, m5.large) - PLATFORM: Operating system (e.g., Windows, Linux) - TENANCY: Instance tenancy (e.g., shared, dedicated) - RECORD_TYPE: Record type (e.g., Usage, Credit, Tax) - LEGAL_ENTITY_NAME: AWS seller of record Note: - Time periods must start and end on the first day of a month, with a duration of exactly one month - The getCostComparisonDrivers operation automatically includes SERVICE and USAGE_TYPE dimensions - Data is available for the last 13 months, or up to 38 months if multi-year data is enabled

free-tier-usage

Retrieves AWS Free Tier usage information using the Free Tier Usage API. This tool provides insights into your AWS Free Tier usage across services: 1. get_free_tier_usage: Shows your current Free Tier usage across AWS services - Helps identify where you are approaching Free Tier limits - Shows actual usage against Free Tier allocations - Supports filtering by service, region, or usage type - Possible Dimensions values are: 'SERVICE'|'OPERATION'|'USAGE_TYPE'|'REGION'|'FREE_TIER_TYPE'|'DESCRIPTION'|'USAGE_PERCENTAGE' - Possible MatchOptions are: 'EQUALS'|'STARTS_WITH'|'ENDS_WITH'|'CONTAINS'|'GREATER_THAN_OR_EQUAL'

rec-details

Get detailed cost optimization recommendation with integrated data from multiple AWS services. This tool combines data from: - Cost Optimization Hub (base recommendation) - AWS Compute Optimizer (detailed metrics for compute resources) - Cost Explorer (Savings Plans/RI purchase recommendations) It provides comprehensive analysis with utilization metrics, savings calculations, and implementation guidance. RESPONSE FORMATTING INSTRUCTIONS: The tool may return both raw recommendation data and a formatting template. When presenting the recommendation: 1. If a template is provided, use it to organize your response 2. If no template is provided, structure your response in a clear, logical manner 3. Always include key information like resource details, savings amounts, and implementation steps 4. Ensure all numeric values (costs, savings, metrics) are included 5. Add natural language explanations to make the information more accessible

ri-performance

Retrieves AWS Reserved Instance (RI) coverage and utilization data using the Cost Explorer API. This tool provides insights into your Reserved Instance (RI) and Savings Plans usage patterns through two main operations: 1. get_reservation_coverage: Shows how much of your eligible usage is covered by RIs - Helps identify opportunities to purchase additional RIs - Supports grouping by dimensions like REGION, INSTANCE_TYPE, etc. - Can filter by specific services, regions, or instance types 2. get_reservation_utilization: Shows how effectively you're using your purchased RIs - Reveals underutilized or idle reserved capacity - Can be grouped by SUBSCRIPTION_ID to see utilization per RI - Helps identify RIs that could be modified or sold in the marketplace Supported dimensions for grouping reservation coverage: - AZ: Availability Zone - INSTANCE_TYPE: Instance type (e.g., m4.xlarge) - LINKED_ACCOUNT: Member accounts in organization - PLATFORM: Operating system - REGION: AWS Region - SERVICE: AWS service (EC2, RDS, etc.) - TENANCY: Instance tenancy (default, dedicated) Reservation utilization can only be grouped by SUBSCRIPTION_ID.

sp-performance

Tool that retrieves AWS Savings Plans coverage and utilization data using the Cost Explorer API. This tool provides insights into your Savings Plans usage patterns through three main operations: 1. get_savings_plans_coverage: Shows how much of your eligible usage is covered by Savings Plans 2. get_savings_plans_utilization: Shows overall utilization metrics for your Savings Plans 3. get_savings_plans_utilization_details: Shows detailed per-Savings Plan utilization

session-sql

Execute SQL queries on the persistent session database. This tool queries tables created by other tools (like cost_explorer_sql) within the current session. All tools share the same database, allowing cross-tool data analysis and joins. Use this tool to: - Query tables created by cost_explorer_sql and other tools - Join data from multiple AWS APIs - Perform complex analysis across different data sources Common queries: - SELECT name FROM sqlite_master WHERE type='table' -- List all tables - SELECT * FROM [table_name] LIMIT 10 -- Preview table data

list-billing-groups

Retrieves a list of billing groups from AWS Billing Conductor. This tool retrieve billing groups for a given billing period. If no billing period is provided, the current billing period is used. The tool returns information about: - Billing group ARN, name, and description - Billing group type (STANDARD or TRANSFER_BILLING) - Billing group status (ACTIVE, PRIMARY_ACCOUNT_MISSING, or PENDING) - Primary account ID - Computation preference (pricing plan ARN) - Account grouping settings (auto-associate, responsibility transfer ARN) - Group size (number of member accounts) - Creation and last modified timestamps You can filter billing groups by: - ARNs: Filter by specific billing group ARNs - Names: Filter by billing group name (supports STARTS_WITH search) - Statuses: Filter by status (ACTIVE, PRIMARY_ACCOUNT_MISSING, PENDING) - Billing group types: Filter by type (STANDARD, TRANSFER_BILLING) - Primary account IDs: Filter by primary account ID - Pricing plan: Filter by pricing plan ARN - Auto-associate: Filter by auto-associate setting - Responsibility transfer ARNs: Filter by responsibility transfer ARNs The tool paginates through results up to max_pages pages (default 10). If more results are available after reaching the page limit, a next_token is returned. Pass the next_token back to this tool to continue fetching from where you left off. Example 1: {"billing_period": "2025-01"} Example 2 (with filter): {"filters": "{"Statuses": ["ACTIVE"], "BillingGroupTypes": ["STANDARD"]}", "billing_period": "2025-01"}

list-account-associations

Lists linked accounts associated with the payer account from AWS Billing Conductor. This tool retrieve linked accounts for a given billing period. If no billing period is provided, the current billing period is used. The tool returns information about each linked account: - Account ID - Account name - Account email - Billing group ARN (if associated to a billing group) You can filter account associations by: - AccountId: Filter by a specific AWS account ID - AccountIds: Filter by a list of AWS account IDs (up to 30) - Association: Filter by association status: - MONITORED: linked accounts associated to billing groups - UNMONITORED: linked accounts not associated to billing groups - Billing Group ARN: linked accounts associated to a specific billing group The tool paginates through results up to max_pages pages (default 10). If more results are available after reaching the page limit, a next_token is returned. Pass the next_token back to this tool to continue fetching from where you left off. Example 1: {"billing_period": "2025-01"} Example 2 (monitored only): {"filters": "{"Association": "MONITORED"}", "billing_period": "2025-01"} Example 3 (by account IDs): {"filters": "{"AccountIds": ["123456789012", "234567890123"]}"}

list-billing-group-cost-reports

Retrieves a summary report of actual AWS charges and calculated AWS charges based on the associated pricing plan of a billing group. This tool retrieve cost reports for billing groups. If no billing period is provided, the current billing period is used. The tool returns cost report information for each billing group: - Billing group ARN - AWS cost (actual AWS charges) - Proforma cost (hypothetical charges based on the associated pricing plan) - Margin (billing group margin) - Margin percentage (percentage of billing group margin) - Currency (displayed currency) You can filter cost reports by: - BillingGroupArns: Filter by specific billing group ARNs (1 to 100 ARNs) Example 1: {"billing_period": "2025-01"} Example 2 (with filter): {"filters": "{"BillingGroupArns": ["arn:aws:billingconductor::123456789012:billinggroup/abc"]}", "billing_period": "2025-01"}

get-billing-group-cost-report

Retrieves the margin summary report for a specific billing group, which includes the AWS cost and charged amount (pro forma cost) broken down by attributes such as AWS service name or billing period. This tool retrieve detailed cost reports for a single billing group, optionally broken down by product name and/or billing period. The tool returns margin summary report results for the billing group: - Billing group ARN - Attributes (key-value pairs for grouping, e.g., PRODUCT_NAME: "S3", BILLING_PERIOD: "Nov 2023") - AWS cost (actual AWS charges) - Proforma cost (hypothetical charges based on the associated pricing plan) - Margin (billing group margin) - Margin percentage (percentage of billing group margin) - Currency (displayed currency) You can customize the report by: - BillingPeriodRange: JSON string specifying a time range (up to 12 months) - GroupBy: JSON array string with values "PRODUCT_NAME" and/or "BILLING_PERIOD" Example 1: {"arn": "arn:aws:billingconductor::123456789012:billinggroup/abc", "group_by": "["PRODUCT_NAME"]"} Example 2: {"arn": "arn:aws:billingconductor::123456789012:billinggroup/abc", "group_by": "["PRODUCT_NAME", "BILLING_PERIOD"]", "billing_period_range": "{"InclusiveStartBillingPeriod": "2025-01", "ExclusiveEndBillingPeriod": "2025-07"}"}

list-custom-line-items

Retrieves a list of custom line items (FFLIs) from AWS Billing Conductor. Custom line items let you allocate costs and discounts to designated AWS accounts within a billing group. Common use cases include allocating support fees, shared service costs, managed service fees, taxes, credits, and distributing RI/Savings Plans savings. This tool retrieve custom line items for a given billing period. If no billing period is provided, the current billing period is used. The tool returns information about: - Custom line item ARN, name, and description - Account ID, billing group ARN - Charge details (type: CREDIT or FEE, flat or percentage) - Computation rule (CONSOLIDATED or ITEMIZED) - Currency code, association size, product code - Presentation details, creation and last modified timestamps You can filter custom line items by: - AccountIds: Filter by AWS account IDs (up to 30) - Arns: Filter by specific custom line item ARNs (up to 100) - BillingGroups: Filter by billing group ARNs (up to 100) - Names: Filter by custom line item names (up to 100) Example 1: {"billing_period": "2025-01"} Example 2 (with filter): {"filters": "{"Names": ["MyCustomLineItem"]}", "billing_period": "2025-01"}

list-custom-line-item-versions

Retrieves a list of versions for a specific custom line item from AWS Billing Conductor. This tool retrieve all versions of a custom line item. If no billing period is provided, the current billing period is used. The tool returns information about each version including charge details, computation rule, billing periods, and timestamps. You can filter versions by: - BillingPeriodRange: Filter by start and/or end billing period Example 1: {"arn": "arn:aws:billingconductor::123456789012:customlineitem/abcdef1234"} Example 2: {"arn": "...", "filters": "{"BillingPeriodRange": {"StartBillingPeriod": "2025-01", "EndBillingPeriod": "2025-06"}}"}

list-resources-associated-to-custom-line-item

Lists the resources associated to a custom line item from AWS Billing Conductor. This tool retrieve resources associated with a specific custom line item. If no billing period is provided, the current billing period is used. The tool returns information about each associated resource: - Resource ARN (can be a billing group or custom line item) - End billing period of the association - Relationship type (PARENT or CHILD) You can filter associated resources by: - Relationship: Filter by relationship type ("PARENT" or "CHILD") Example 1: {"arn": "arn:aws:billingconductor::123456789012:customlineitem/abcdef1234"} Example 2: {"arn": "...", "filters": "{"Relationship": "CHILD"}", "billing_period": "2025-01"}

list-pricing-rules

Retrieves a list of pricing rules from AWS Billing Conductor. This tool retrieve pricing rules for a given billing period. The tool returns information about: - Pricing rule ARN, name, and description - Type (MARKUP, DISCOUNT, or TIERING) - Scope (GLOBAL, SERVICE, BILLING_ENTITY, or SKU) - Modifier percentage, associated pricing plan count - Service, operation, usage type, billing entity - Tiering configuration, creation and last modified timestamps You can filter pricing rules by: - Arns: Filter by specific pricing rule ARNs Example 1: {"billing_period": "2025-01"} Example 2: {"filters": "{"Arns": ["arn:aws:billingconductor::123456789012:pricingrule/abc"]}", "billing_period": "2025-01"}

list-pricing-plans

Retrieves a list of pricing plans from AWS Billing Conductor. This tool retrieve pricing plans for a given billing period. If no billing period is provided, the current billing period is used. The tool returns information about: - Pricing plan ARN, name, and description - Number of associated pricing rules (size) - Creation and last modified timestamps You can filter pricing plans by: - Arns: Filter by specific pricing plan ARNs Example 1: {"billing_period": "2025-01"} Example 2: {"filters": "{"Arns": ["arn:aws:billingconductor::123456789012:pricingplan/abc"]}", "billing_period": "2025-01"}

list-pricing-rules-for-plan

Lists the pricing rules associated with a specific pricing plan. This tool retrieve pricing rules associated with a specific pricing plan If no billing period is provided, the current billing period is used. The tool returns information about: - The billing period for which the pricing rule associations are listed. - The optional pagination token to be used on subsequent calls. - The ARN of the pricing plan for which associations are listed. - A list containing pricing rules that are associated with the requested pricing plan Example: {"pricing_plan_arn": "arn:aws:billingconductor::123456789012:pricingplan/abc"}

list-pricing-plans-for-rule

Lists the pricing plans associated with a specific pricing rule. This tool retrieve pricing plans associated with a specific pricing rule If no billing period is provided, the current billing period is used. The tool returns information about: - The billing period for which the pricing rule associations are listed. - The optional pagination token to be used on subsequent calls. - The ARN of the pricing rule for which associations are listed. - The list containing pricing plans that are associated with the requested pricing rule. Example: {"pricing_rule_arn": "arn:aws:billingconductor::123456789012:pricingrule/abc"}

FAQ

Frequently asked questions about AWS Billing

Which operations handle large billing datasets fastest?+

Cost Explorer and AWS Pricing tools completed in under 50ms during our tests, making them efficient for frequent cost lookups. Session SQL queries executed in 6ms, providing rapid access to billing data once connected. These fast operations contrast with comprehensive budget analysis which required 1905ms to process complete budget configurations across accounts.

What latency should I expect for budget operations?+

Budget queries took 1905ms in our sandbox tests, representing the longest operation we measured. This reflects the complexity of budget calculations spanning multiple accounts and time periods. Most other billing operations like cost anomaly detection and free tier usage completed within 700-800ms, providing faster access to focused billing insights.

How does the server handle billing operations that require account-wide data aggregation?+

Operations pulling comprehensive account data show varied performance patterns. List operations for billing groups, account associations, and custom line items completed within 550-850ms. Pricing rules analysis required 1046ms, while pricing plans loaded in 336ms. The variance reflects different data complexity levels across AWS billing components.

What happens when write operations are blocked in the billing context?+

During testing, 13 tools were not executed due to write-dangerous classifications, including budget modifications and billing configuration changes. The server protects against unintended billing changes while maintaining full read access to cost data, usage reports, and pricing information through the 12 successfully executed tools.

Which billing data sources provide the most responsive access?+

Pricing data queries and SQL session establishment showed sub-10ms response times in our tests. Cost Explorer delivered results in 47ms, making these tools suitable for applications requiring frequent cost lookups. Compute Optimizer and anomaly detection maintained consistent 700ms response times for their more complex analytical operations.

How does the server perform across different AWS billing service categories?+

Core billing services like Cost Explorer and pricing tools executed rapidly under 50ms. Usage monitoring tools including free tier tracking and compute optimization maintained 700-720ms response times. Administrative operations for billing groups and account management completed within 550-850ms, showing consistent performance across service categories.

Related

Explore more

Testing History

1 runlive_runtimeApr 7, 2026
protocol10/10reliability10/10

Community

Community Reviews

No community reviews yet. Be the first to share your experience!

Write a Review

Overall
Ease of Setup
Documentation
Reliability

0 / 5000