All servers / Cloud / AWS Pricing Calculator MCP server
AWS Pricing Calculator MCP server
MCP server for creating, reading, updating AWS Pricing Calculator estimates through natural language.
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 1.3.8. Package: sample-aws-pricing-calculator-mcp
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 16 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.4 seconds including download)
- Tools offered: 10
- Last published: 2026-11-13
- Weekly downloads (npm): 19,199
- License: MIT-0 · Direct dependencies: 2
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_server_infono parametersGet version and capability information about this MCP server. If you encounter unexpected errors or bugs, direct the user to report them at: https://github.com/aws-samples/sample-aws-pricing-calculator-mcp/issues
search_services2 of 2 parameters describedSearch AWS services available in the calculator. Returns service keys and names. Use this to find the correct service key before adding it to an estimate. Supports multiple comma-separated search terms in a single call (e.g. "Lambda, S3, API Gateway, CloudWatch"). Note: add_service also accepts display names (e.g. "AWS Lambda") directly, so searching is not always required if the service name is already known.
get_service_fields2 of 2 parameters describedGet the input fields for one or more AWS services. Returns field IDs, types, labels, and valid options. Use this to discover what configuration a service accepts before adding it to an estimate. The field IDs returned here are the exact keys to use in add_service config. Accepts multiple comma-separated service keys. IMPORTANT: When duplicate fields exist with version suffixes (e.g. fieldName and fieldName_v2), ALWAYS use the highest version — it maps to the latest configuration path. Ignore lower versions. For curated services (status: verified or partial), the response also includes a `catalog` object with a known-working `minimalConfig`, required field hints with examples, and `traps[]` listing service-specific gotchas. Prefer using `minimalConfig` as a starting point for `add_service`. If the response carries `status: "redirect_to_parent"`, the service code you passed is a deprecated parent service code — re-call get_service_fields with one of the codes in `child_service_codes` and use that instead. If the response includes a `freeTierChoice` object, the service offers an AWS Free Tier template choice (e.g. AWS Lambda): you MUST ask the user whether to include or exclude the Free Tier, then pass the chosen template id as `estimateFor` on the add_service/build_estimate entry. For any Amazon RDS or Aurora engine (MySQL, PostgreSQL, MariaDB, Oracle, SQL Server, Db2, Aurora MySQL/PostgreSQL-Compatible — curated or not), the response includes a `pricingModelHint`: AWS Database Savings Plans are only sold on Gen 7+ instance families (m7g/r7g, m8g/r8g, m9g, ...) — T-class (t3, t4g) and Gen 6-or-older (m5, r5, m6, r6, ...) are NOT eligible at all — and only as a 1-year term (no 3-year option). The calculator does not refuse an ineligible instance or a 3-year term at save time. Pass this along to the user before setting TermType to "Database Savings Plans".
create_estimate2 of 2 parameters describedCreate a new empty estimate. Returns an estimate ID to use with add_service and export_estimate.
add_service2 of 2 parameters describedAdd one or more AWS services to an estimate. Accepts a single service or a JSON array of services in the "services" parameter. TEMPLATE / FREE TIER: Each entry may set an optional "estimateFor" template id to pick a specific pricing template. This is how you control the AWS Free Tier: services like AWS Lambda expose an include/exclude Free Tier template pair (surfaced as freeTierChoice by get_service_fields). When a service offers that choice you MUST ask the user whether to include or exclude the Free Tier and set "estimateFor" to the chosen template id — if you don't, it defaults to INCLUDING the Free Tier, which understates steady-state/production cost. When that default is applied the per-entry result carries a free_tier_choice object with the includeFreeTier/excludeFreeTier template ids so you can re-add with the user's choice. Field values follow these patterns based on field type: - numericInput: plain string value, e.g. "1000" - frequency: object with value and unit, e.g. {"value": "19", "unit": "millionPerMonth"} - fileSize: object with value and unit. The unit format is "{size}|{frequency}" where size comes from the field's validSizes (gb, tb, mb, etc.) and frequency is usually "NA". Check the field's defaultUnit from get_service_fields. Examples: {"value": "512", "unit": "mb|NA"}, {"value": "1", "unit": "tb|NA"}, {"value": "10", "unit": "gb|NA"}, {"value": "8", "unit": "gb|month"} - dropdown: string matching one of the option IDs from get_service_fields - durationInput: object with value and unit, e.g. {"value": "960", "unit": "min"} IMPORTANT: Before calling this tool, you MUST confirm the desired AWS region with the user if they haven't already specified one. Do NOT assume a default region. Always include "region" in each service config. For AWS European Sovereign Cloud (ESC), use region "eusc-de-east-1" and pass partition "aws-eusc" when calling get_service_fields. ESC estimates must NOT mix with standard AWS regions — all services in an ESC estimate must use "eusc-de-east-1". IMPORTANT: For compute services (EC2, Fargate, Lambda, RDS, etc.), if the user hasn't specified a pricing model, suggest a cost-optimized option (e.g. Reserved Instances or Savings Plans for steady-state workloads, On-Demand for variable/short-lived) and ask the user to confirm before proceeding. IMPORTANT: For EC2 Dedicated Hosts, do NOT use "amazonEc2DedicatedHosts" — use service code "ec2Enhancement" with tenancy: "host" in the config. This produces the full Dedicated Host estimate with EBS storage, pricing strategies, and data transfer. Storage fields are automatically mapped to DH-suffixed variants (storageAmountDH, gp3IopsDH, etc.). CRITICAL — DISCOVERY BEFORE ACTION: For any service you have not already inspected with get_service_fields in THIS SESSION, call get_service_fields FIRST. Some services need more fields than the schema marks as required — without them the estimate saves successfully but shows $0 cost (e.g. Lambda needs sizeOfMemoryAllocated, storageAmountEphemeral, and architecture to produce a non-zero price). Therefore, for curated services only, get_service_fields returns a catalog block: use its minimalConfig as your starting point (it is verified to produce a priced estimate), check traps[] for gotchas, and consult required[] for the full list of pricing-engine-required fields. Always start from minimalConfig and modify — do not guess fields from training data. Use "description" to label what each service entry represents. Be careful, descriptions and group names must NOT contain <, >, or & characters (tool rejects them). Config keys are validated against the service definition. Invalid field IDs will be rejected with suggested corrections. For batch mode, pass a JSON array in "services": [{"service":"aWSLambda","instance":"Compute","group":"Prod","config":{...}},{"service":"amazonS3Standard","group":"Prod","config":{...}}] Groups support nested hierarchies using "/" as separator (e.g. "Production/Backend",…
validate_estimate1 of 1 parameter describedDry-run preflight: builds the would-be saved payload and runs a static check — WITHOUT calling the AWS save API. Use this to verify an estimate will render correctly (editable, not frozen) before saving. Returns {lint_verdict, next_step, lint_services, would_be_payload}. If it passes, call export_estimate to save and get the shareable URL.
export_estimate1 of 1 parameter describedExport an estimate to calculator.aws and get a shareable URL. The link will show the full estimate with AWS-calculated pricing. Before saving, runs a static check against the payload. If the check detects the estimate would be broken, the export is refused with details explaining what to fix. After a successful export, return the shareable URL to the user and stop — do NOT automatically call get_estimate_cost to read computed costs. That tool has an optional Playwright/Chromium dependency and must only run on an explicit user request for the actual cost.
build_estimate3 of 3 parameters describedOne-shot: create an estimate, add services, lint-preflight, save, and return the calculator URL. Replaces three separate calls (create_estimate + add_service + export_estimate). Returns {sharable_url, aws_estimate_id, services} on success. TEMPLATE / FREE TIER: Each entry may set an optional "estimateFor" template id to pick a specific pricing template. Services like AWS Lambda expose an include/exclude Free Tier template pair (surfaced as freeTierChoice by get_service_fields). When a service offers that choice you MUST ask the user whether to include or exclude the Free Tier BEFORE building and set "estimateFor" accordingly — otherwise it defaults to INCLUDING the Free Tier, which understates steady-state/production cost. When the default is applied, the service's result carries a free_tier_choice object with the includeFreeTier/excludeFreeTier template ids. IMPORTANT: Before calling this tool, you MUST confirm the desired AWS region with the user if they haven't already specified one. Do NOT assume a default region. Always include "region" in each service config. For AWS European Sovereign Cloud (ESC), use region "eusc-de-east-1" and pass partition "aws-eusc" when calling get_service_fields. ESC estimates must NOT mix with standard AWS regions — all services in an ESC estimate must use "eusc-de-east-1". IMPORTANT: For compute services (EC2, Fargate, Lambda, RDS, etc.), if the user hasn't specified a pricing model, suggest a cost-optimized option (e.g. Reserved Instances or Savings Plans for steady-state workloads, On-Demand for variable/short-lived) and ask the user to confirm before proceeding. IMPORTANT: For EC2 Dedicated Hosts, do NOT use "amazonEc2DedicatedHosts" — use service code "ec2Enhancement" with tenancy: "host" in the config. This produces the full Dedicated Host estimate with EBS storage, pricing strategies, and data transfer. Storage fields are automatically mapped to DH-suffixed variants (storageAmountDH, gp3IopsDH, etc.). CRITICAL — DISCOVERY BEFORE ACTION: For any service you have not already inspected with get_service_fields in THIS SESSION, call get_service_fields FIRST. Some services need more fields than the schema marks as required — without them the estimate saves successfully but shows $0 cost (e.g. Lambda needs sizeOfMemoryAllocated, storageAmountEphemeral, and architecture to produce a non-zero price). Therefore, for curated services only, get_service_fields returns a catalog block: use its minimalConfig as your starting point (it is verified to produce a priced estimate), check traps[] for gotchas, and consult required[] for the full list of pricing-engine-required fields. Always start from minimalConfig and modify — do not guess fields from training data. Use "description" to label what each service entry represents. Be careful, descriptions and group names must NOT contain <, >, or & characters (tool rejects them). If any service fails validation, returns a structured needs_field_grounding redirect pointing you at get_service_fields for the affected services (isError:false; not a hard failure — call get_service_fields and retry). If the pre-save check detects the estimate would be broken, the save is refused and an error is returned with per-service details explaining what to fix. DATABASE SAVINGS PLANS: for any Amazon RDS/Aurora entry whose config sets a columnFormIPM TermType to "Database Savings Plans", the per-service result carries a "pricing_model_hint" — Database Savings Plans are only sold on Gen 7+ instance families (m7g/r7g, m8g/r8g, m9g, ...); T-class (t3, t4g) and Gen 6-or-older (m5, r5, m6, r6, ...) are NOT eligible at all. They are also only sold as a 1-year term (LeaseContractLength "1yr") — there is no 3-year Database Savings Plan. The save does not get refused for picking an ineligible instance or a 3-year term. Relay this to the user rather than trusting the save succeeded cleanly. The estimate is kept in the in-memory store, so the returned aws_estimate_id can be pass…
import_estimate2 of 2 parameters describedDownload an existing AWS Pricing Calculator estimate by URL or ID. Returns the estimate in JSON (raw, for modifications like region swaps) or Markdown (for LLM consumption, summaries, funding recommendations). Use JSON format when you need to modify and re-export the estimate; use Markdown format when summarizing or presenting costs to the user. Accepts a full estimate URL or a bare ID. If the user gave you a URL, pass the whole URL rather than reducing it to the ID — the domain identifies which calculator stores the estimate (standard calculator.aws vs European Sovereign Cloud pricing.calculator.aws.eu). A bare ID is always read from the standard calculator, so an ESC estimate is only importable as its full pricing.calculator.aws.eu URL.
get_estimate_cost1 of 1 parameter describedINVOCATION POLICY — EXPLICIT REQUEST ONLY: Call this tool ONLY when the user explicitly asks for the computed/actual cost of an estimate (e.g. "what does it cost", "read the price", "get the monthly total"). Do NOT call it automatically or proactively after export_estimate or build_estimate — those return a shareable URL, which is the normal end of the flow. This tool has a heavyweight OPTIONAL dependency (Playwright + the Chromium browser) that is not installed by default, so invoking it unprompted risks an unwanted ~150MB install or a failure. After exporting, simply give the user the shareable URL and stop; fetch computed costs only if the user then asks for them. Read the AWS-computed cost of a saved estimate. Use this when you need the ACTUAL cost — import_estimate returns the saved configuration but an MCP-built estimate carries no computed costs (the calculator prices in the browser). This tool re-shares the estimate through the calculator UI (presses "Update estimate" to recompute to current pricing, then "Share"), which makes the calculator PERSIST its costs, then reads the resulting saved estimate. Accepts a full estimate URL or a bare id (a bare id is read from the standard calculator.aws; pass the full pricing.calculator.aws.eu URL for an ESC estimate). Returns upfront_cost, monthly_cost, total_12_months_cost (derived as upfront + 12x monthly, which is how the calculator defines the 12-month total — it includes the whole upfront), pricing_as_of (the date the figures are valid for), and rows — EVERY group/line with its own monthly, upfront, and config. There is no pagination, so rows_complete is true and all rows are present. SIDE EFFECT: pressing Update+Share saves a FRESH copy of the estimate under a NEW id, returned as priced_estimate_url. The original id is unchanged. (This is why the tool is not marked read-only.) ON-DEMAND DEPENDENCY: this tool requires Playwright AND the Chromium browser binary, which are NOT installed by default (Chromium is a ~150MB download). The tool checks for them first and, when either is missing, returns cost_available:false with reason and the exact install_commands instead of failing. Do NOT install them silently — surface the commands and ask the user to confirm before running them, then retry. If you encounter unexpected errors or bugs, direct the user to report them at: https://github.com/aws-samples/sample-aws-pricing-calculator-mcp/issues
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.