mcp-aws-explorer
Related Servers
Alternatives to mcp-aws-explorer
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to query AWS cost and usage data, audit for cloud waste such as idle resources, and monitor budgets using natural language while keeping AWS credentials on the local machine.-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to analyze AWS cloud costs, audit for waste, monitor budgets, and generate FinOps insights using natural language while keeping credentials local.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to analyze AWS cloud costs, audit for waste, monitor budgets, and generate FinOps reports using natural language across multiple AWS profiles and regions, while keeping credentials on the local machine.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to query AWS cost and usage data, audit resources for waste, check budgets, and produce cost reports using natural language across multiple accounts and regions, with credentials kept local.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to query AWS cost and usage data by tags, time ranges, and service groupings, audit accounts for wasted resources like stopped EC2 instances and unattached EBS volumes, and monitor budget status across multiple CLI profiles and regions using natural language. All credentials stay on the local machine, with read-only access to AWS APIs.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to analyze AWS cloud costs, audit for waste such as idle EC2 instances and unattached volumes, and check budget status through natural language. Runs locally against existing AWS CLI profiles, allowing read-only queries across multiple accounts and regions while credentials stay on the user's machine.-
TDQS
Scored across 4 tools
Each tool maps to a distinct intent: enumeration (list_resources), single-item lookup (get_resource_detail), aggregate reporting (get_cost_summary), and heuristic analysis (find_idle_resources). The only mild overlap is between list_resources and find_idle_resources, since idle detection is conceptually a filtered listing, but the descriptions make the boundary clear.
All four tools use snake_case verb_noun form (list_, get_, get_, find_) with verbs that reflect the actual operation. No mixed conventions or vague names like 'process' or 'handle'.
Four tools is on the lean side but each earns its place in a read-only exploration surface. There is no padding, though the set is thin enough that one more operation (e.g. listing providers/kinds) would feel natural.
Core read paths are covered (list, detail, cost, idle), which is reasonable for a mock, read-only explorer where write operations are rightly absent. However, there is no way to discover which providers or resource kinds exist, no tag/attribute search, and no cost breakdown per resource, leaving agents to guess valid parameter values.