Deployed an AWS Serverless/Lambda version of a MCP server/client via SAM CLI. AWS Community Tutorial

Using SAM CLI by default these days and I greatly prefer it over the UI/web version. The tutorial had some flaws. I prefer python code for backend, it is easier to transform and manipulate data using python libs compared to Typescript.

After all that troubleshooting, I see this section on the MCP website SPECIFICALLY for vibe coding: MCP Vibe coding Prompts

I am all for pair programming with LLMs, it is because it of that I am more a polyglot these days and it gets me up and running really quick. However, there is too many considerations for my generative chat sessions to keep in context to put up a simple page that preserves backend integrity, maintains speed and etc. It still requires a lot more work to go in and fine tune it. It is mildly disturbing to me that this is the … presumed typical way so much so that it is a line item on the MCP website.

But… Chesterton’s fence, I give every new thing a fair shot.

I made a simple diagram (any excuse to practice diagramming with DiagramsAsCode) to show the architecture of what was implemented and checked it into Github as well.

Github code: MCP - AWS Serverless