Registry / aws / awslabs-aws-pricing-mcp-server

awslabs-aws-pricing-mcp-server

library1.0.31pypypiunverified

The AWS Pricing MCP Server (Model Context Protocol) is an open-source tool developed by AWS Labs that enables AI assistants to access real-time AWS pricing data, providing cost estimates and insights through natural language queries. Currently at version 1.0.27, it receives frequent updates, often tied to the broader `awslabs/mcp` repository's release cadence, which can be daily or weekly with minor fixes and feature enhancements. [1, 2, 6, 8]

aws llm-agents

pip install awslabs-aws-pricing-mcp-server

github ↗package ↗homepage ↗docs ↗changelog ↗

INSTALL

IMPORT

SIG · AWSLABS-AWS-PRICIN

awslabs-aws-pricing-mcp-server

awspythonv1.0.31

Install

—

Import

—

Disk

—

Pass rate

0/ 10

Env Coverage0 / 10

glibc

3.9–3.13

musl

3.9–3.13

Install & Compatibility

Where this runs

tested against v? · pip install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

py 3.10–3.920 runs

build_error

glibc

py 3.10–3.920 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

AWS Pricing MCP Server

✓ The AWS Pricing MCP Server is designed to be run as a standalone process, typically invoked via a command-line utility like 'uvx' from an MCP-compatible client (e.g., Amazon Q CLI, Kiro, Cursor, VS Code). Direct programmatic import of its server components for end-user application logic is not the primary use case. Its entry point is usually a `main()` function executed as a script. [18, 19, 21]

This is a server, not a library intended for direct module imports in user applications.

To get started, configure your MCP-compatible client (such as Kiro, Cursor, or Amazon Q CLI) by adding the AWS Pricing MCP Server definition to its configuration file (e.g., `~/.kiro/settings/mcp.json`). Ensure you have `uv` installed and AWS credentials configured with appropriate permissions (`pricing:*`). Replace `your-aws-profile` with your AWS CLI profile name or ensure `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables are set. [8, 18, 21]

{ "mcpServers": { "awslabs.aws-pricing-mcp-server": { "command": "uvx", "args": [ "awslabs.aws-pricing-mcp-server@latest" ], "env": { "AWS_PROFILE": "your-aws-profile", "FASTMCP_LOG_LEVEL": "ERROR" } } } }

Debug

Known issues

breakingServer Sent Events (SSE) support was removed in version 1.0.0 (May 26, 2025). This aligns with the Model Context Protocol specification's backwards compatibility guidelines and prepares for Streamable HTTP transport.

fix

Migrate your MCP client to use alternative transport methods (e.g., stdio or Streamable HTTP when available) or, if absolutely necessary, use an older major version of the server that still supports SSE. [3, 5]

affects: >=1.0.0

gotchaThe AWS Pricing MCP Server provides *estimated* pricing information based on AWS Pricing APIs and web pages. These estimates are intended for pre-deployment planning and may not reflect actual deployed cloud service expenses. AI assistants might also not always construct filters correctly or identify the absolute cheapest options.

fix

Always cross-reference with official AWS billing statements and the AWS Pricing Calculator for exact costs. Treat server outputs as guidance for planning, not final figures. [4, 8]

affects: All

gotchaAWS credentials with `pricing:*` permissions are required for the server to access the AWS Pricing API. Without these, the server will not be able to fetch pricing data.

fix

Configure your AWS CLI with an IAM role or user that has a policy granting `pricing:*` permissions (e.g., `pricing:GetProducts`, `pricing:DescribeServices`). This can be done via `aws configure` or environment variables (e.g., `AWS_PROFILE`, `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`). [8]

affects: All

deprecatedThe `awslabs.core-mcp-server`, which bundled many individual MCP servers, is deprecated. It had issues with massive dependency footprints, slow installs, and tool name conflicts. Users are now advised to configure individual MCP servers directly.

fix

Remove `core-mcp-server` from your MCP client configuration and add `awslabs.aws-pricing-mcp-server` (and other required servers) individually. This gives faster installs and direct control. [9]

affects: All versions where `core-mcp-server` was used as a proxy.

Upgrade

Version history

1.0.31latest on PyPI · released Jun 9, 2026

Audit

Dependencies

uvrequiredRecommended package manager for installation and execution of MCP servers.

boto3requiredUsed internally for AWS API interactions, requires AWS credentials configured.

Agent activity

20 hits · last 30 days

node

Amazon

OpenAI (training)

Resources

githubhttps://github.com/awslabs/mcp ↗

packagehttps://pypi.org/project/awslabs-aws-pricing-mcp-server/ ↗

homepagehttps://awslabs.github.io/mcp/ ↗

docshttps://awslabs.github.io/mcp/servers/aws-pricing-mcp-server/ ↗

changeloghttps://github.com/awslabs/mcp/blob/main/src/aws-pricing-mcp-server/CHANGELOG.md ↗