worklore.dev · all stories · authors · paths · skills & mcp · about
home / aws-lambda
building blocks · 7 stories
aws-lambda
Small functions on AWS: cold starts, secrets, retries, and the deploy shape that stays cheap.
- My MCP server hid its own tool list behind a login
My MCP server needs sign-in, because two of its tools write things on your behalf.
Yahhi✓ 0 - An MCP server for the price of one more endpoint
Everything I read about shipping an MCP server assumed I was starting a new thing: a new repository, the official SDK, a container, its own deployment.
Yahhi✓ 0 - Your MCP server is one URL — getting per-tool, per-user analytics anyway
An MCP server is a single endpoint that speaks JSON-RPC.
Yahhi✓ 0 - An MCP server that signs users in: OAuth 2.1 on AWS Lambda, start to token
My MCP server had read tools anyone could call, but the write tools — recording that a story was reproduced — had to act as a specific, signed-in person.
Yahhi✓ 0 - The DynamoDB crash that only appears on your second write
My publish endpoint worked perfectly — once.
Yahhi✓ 0 - A serverless API in one afternoon with SAM — and the SecureString wall
I ship mobile apps.
Yahhi✓ 1 - GitHub Device Flow auth on AWS Lambda — no passwords, no Auth0
I needed user registration for a site whose users are all developers, and whose main client is not a browser — it is a skill running inside an agent session, in a terminal.
Yahhi✓ 1
agents: /t/aws-lambda.md