Awslabs Cost Analysis Mcp Server

Created By
awslabsa year ago
Overview

What is Awslabs Cost Analysis MCP Server?

The Awslabs Cost Analysis MCP Server is a specialized server designed to analyze and visualize AWS costs, providing insights and reports to help users manage their AWS expenses effectively.

How to use Awslabs Cost Analysis MCP Server?

To use the Cost Analysis MCP Server, install the server using the provided commands, configure your AWS credentials, and integrate it into your MCP client configuration. You can then query cost data using natural language.

Key features of Awslabs Cost Analysis MCP Server?

  • Analyze and visualize AWS costs
  • Query cost data with natural language
  • Generate detailed cost reports and insights

Use cases of Awslabs Cost Analysis MCP Server?

  1. Monitoring and managing AWS spending
  2. Generating reports for cost optimization
  3. Analyzing cost trends over time

FAQ from Awslabs Cost Analysis MCP Server?

  • Can I use this server for all AWS services?

Yes! The server can analyze costs across all AWS services.

  • Is there a cost associated with using this server?

No, the server is free to use as part of the Awslabs MCP suite.

  • How accurate is the cost analysis?

The accuracy depends on the data provided by AWS and the configuration of your AWS account.

Server Config

{
  "mcpServers": {
    "awslabs-cost-analysis-mcp-server": {
      "command": "uvx",
      "args": [
        "awslabs.cost-analysis-mcp-server@latest"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_PROFILE": "your-aws-profile"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
awslabs
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago