MCP for AWS Cost Explorer and CloudWatch logs
MCP for AWS Cost Explorer and CloudWatch logs. Exposed over MCP by the a sample for understanding cloud spend mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
subgraph "Claude Desktop" Host --> MCPClient[MCP Client] end
This tool provides a convenient way to analyze and visualize AWS cloud spending data using Anthropic's Claude model as an interactive interface. It functions as an MCP server that exposes AWS Cost Explorer API functionality to Claude Desktop, allowing you to ask questions about your AWS spend in natural language.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
Prerequisites — The Prerequisites tool exposed by this serverYou will need 6 environment variables: AWS_PROFILE, AWS_REGION, BEDROCK_LOG_GROUP_NAME, MCP_TRANSPORT, MCP_SERVER_URL, MCP_SERVER_PORT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. A Sample For Understanding Cloud Spend's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by aws-samples; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"aws-cost-explorer": {
"command": "docker",
"args": [ "run", "-i", "--rm", "-e", "AWS_PROFILE", "-e", "AWS_REGION", "-e", "BEDROCK_LOG_GROUP_NAME", "-e", "MCP_TRANSPORT", "aws-cost-explorer-mcp:latest" ],
"env": {
"AWS_PROFILE": "YOUR_AWS_PROFILE_NAME",
"AWS_REGION": "us-east-1",
"BEDROCK_LOG_GROUP_NAME": "YOUR_CLOUDWATCH_BEDROCK_MODEL_INVOCATION_LOG_GROUP_NAME",
"MCP_TRANSPORT": "stdio"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AWS_PROFILE | Configuration value read at startup. | Optional |
| AWS_REGION | Configuration value read at startup. | Optional |
| BEDROCK_LOG_GROUP_NAME | Configuration value read at startup. | Optional |
| MCP_TRANSPORT | Configuration value read at startup. | Optional |
| MCP_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_SERVER_PORT | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.