mcp-aws-explorer
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-aws-explorer
A Model Context Protocol (MCP) server in TypeScript that lets an AI assistant explore an AWS account's inventory and costs through read-only tools — list resources, inspect one resource, summarize cost by service, and find idle resources that are quietly costing money.
It runs entirely against a local mock dataset (synthetic JSON, no real AWS account, no credentials), so it is safe to run, demo, and test anywhere.
What this demonstrates
Model Context Protocol (MCP) server design with the official TypeScript SDK
Tool use / function calling patterns for LLM agents: typed inputs (Zod), structured JSON outputs, explicit error results
TypeScript on Node.js with stdio transport (the standard for local MCP servers)
AWS domain modeling: S3, Lambda, and cost-by-service (Cost Explorer–style) data
Serverless / cloud cost visibility: idle-resource detection, the same pattern used to find wasted spend in real accounts
Safe-by-default engineering: read-only tools, no credentials, no network calls
Related MCP server: AWS FinOps MCP Server
Architecture
MCP client (Claude Desktop, Cursor, an agent framework, ...)
| JSON-RPC over stdio
v
src/index.ts (McpServer, 4 tools, Zod-validated inputs)
|
v
src/data/mock-aws.json (synthetic S3 buckets, Lambda functions, cost by service)src/index.ts— the server: tool definitions, handlers, stdio transport.src/data/mock-aws.json— the synthetic dataset. Swap this module for real AWS SDK calls (S3ListBuckets, LambdaListFunctions, Cost ExplorerGetCostAndUsage) and the tool surface stays identical — that swap is the documented extension path.scripts/smoke-test.mjs— end-to-end test: spawns the server over stdio, performs the MCP initialize handshake, lists tools, and calls tools.
Tools
Tool | Input | Returns |
|
| Buckets and/or functions with region, size, runtime, usage signals |
|
| Full record for one bucket or function (explicit error if not found) |
| — | Current vs. previous month totals, per-service cost and % change, top service |
|
| Buckets not accessed / functions not invoked within the threshold, each with a reason |
Run it
npm install
npm run build
npm start # speaks MCP over stdio; logs go to stderrConnect an MCP client
Example configuration (Claude Desktop claude_desktop_config.json, or any
MCP client that takes an mcpServers map):
{
"mcpServers": {
"aws-explorer": {
"command": "node",
"args": ["/absolute/path/to/mcp-aws-explorer/dist/index.js"]
}
}
}Then ask the assistant things like:
"What Lambda functions do I have, and which runtimes are they on?"
"What did I spend this month, and what changed versus last month?"
"Find resources that have been idle for 60+ days."
Test
npm run build
npm run smokeThe smoke test spawns the compiled server, completes the MCP handshake,
verifies all four tools are listed, and calls find_idle_resources and
get_cost_summary against the mock dataset.
Verified output:
PASS: initialize handshake (server: mcp-aws-explorer)
PASS: tools/list includes list_resources
PASS: tools/list includes get_resource_detail
PASS: tools/list includes get_cost_summary
PASS: tools/list includes find_idle_resources
PASS: find_idle_resources found idle resources (count=4)
PASS: find_idle_resources flags demo-legacy-backups-2019
PASS: get_cost_summary totals $319.25 across 6 services
All smoke tests passed.License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Discover Frontier inference capabilities and read sanitized usage through read-only tools.
Read-only AI/LLM cost tools with current MCP discovery and attributable Registry transport.
FinOps assistant: query AWS, GCP and Azure cost, commitments, budgets and reports.
Unified API to query AWS, GCP, Azure and generate Terraform/CLI execution kits for AI agents.
Related MCP Servers
- 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 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.-
- 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.-