If you have built an estimate in the AWS Pricing Calculator by hand, you know the drill. Open calculator.aws, search a service, click in, stare at twenty fields half of which you do not need, guess at the ones the form does not explain, pick a region, repeat for every service. Then redo the whole thing next week when the customer asks what it looks like in Frankfurt.
For presales that is not a small annoyance. It is the gap between giving a number on the call and saying "let me get back to you." I wired the - it opens in the calculator with all four services priced and grouped under "Prod," ready to edit or hand off. I never opened a browser to make it.
The preflight is the part I lean on. Some calculator fields are optional to the save API but required by the pricing engine - leave one out and the estimate saves at $0. On my first pass it caught that EC2 needed tenancy set and flagged it instead of saving a wrong number. A confidently wrong estimate is worse than no estimate, so a tool that refuses to ship one is doing me a favor.
Import, swap region, re-export
The other half of presales is reworking last quarter's estimate, not starting fresh. The MCP imports any estimate by URL or ID - as JSON to edit (swap the region, bump the counts, re-export) or as Markdown to hand an LLM for analysis. The region-swap loop drops from "rebuild it in the UI" to import, change one field, export.
Why it matters for presales
The old loop: gather requirements, spend twenty minutes clicking them in, fat-finger a field, redo it, reply by end of week. The estimate was the bottleneck.
The new loop: describe the architecture while the customer is still on the call, get a shareable URL before it ends. "Actually it is closer to 80 million requests" - fine, update it, the link is still warm. The estimate moves to where the requirements live, which is the conversation. That is the real change, more than the speed.
Running it
It is an AWS Samples repo, so install follows the README: clone it, install deps, register it as an MCP server in your client. After that you do not call tools by name - you describe the architecture and let the agent reach for them in order. Source, the verified configs, and setup are in the .
SOCIAL SHARE CARD GENERATOR