aws-billing-mcp

MCP server (stdio) — accesses Billing and Cost Management data for <目标AWS 账号> via the local AWS CLI, for MCP clients such as Quick Desktop to perform cost and usage analysis.

Prerequisites

• Node.js ≥ 18 (v24 is installed on this machine)

• AWS CLI v2, and the credentials of the default profile (or the profile specified by AWS_PROFILE) belong to <目标AWS 账号>

• IAM permissions: ce:Get*, budgets:ViewBudget, sts:GetCallerIdentity

On the first tool invocation, the server uses sts get-caller-identity to verify that the current credentials indeed belong to <目标AWS 账号>. If they do not match, it immediately returns an error, preventing accidental queries against other accounts.

Related MCP server: aws-cost-mcp

Installation

cd ~/aws-billing-mcp
npm install

Smoke Test

node test-client.mjs

It will list all tools, query the Top 5 costs for this month grouped by service, and run a month-end cost forecast.

Integrating with Quick Desktop

Add the following to Quick Desktop's MCP server configuration (Settings → Integrations/MCP servers, or its JSON configuration file):

{
  "mcpServers": {
    "aws-billing": {
      "command": "node",
      "args": ["~/aws-billing-mcp/index.mjs"],
      "env": {
        "AWS_PROFILE": "default"
      }
    }
  }
}

Note: node is installed via nvm (~/.nvm/versions/node/v24.8.0/bin/node). If Quick Desktop cannot find node or aws at startup, replace command with the absolute path to node, and add "PATH": "/usr/local/bin:/usr/bin:/bin:/opt/homebrew/bin" to env (include the directory containing aws).

Tool List

Typical Analysis Questions (in Quick Desktop)

• “How much did this account spend this month? Rank the Top 10 by service.”

• “What is the daily Bedrock consumption trend for the last 30 days? Are there any abnormal spikes?”

• “Forecast the total bill at the end of August.”

• “Break down EC2 costs by usage type — which part is growing the fastest?”

Environment Variables