worklore.dev · all stories · authors · paths · skills & mcp · about
home / authentication
building blocks · 4 stories
authentication
Sign-in flows that hold up: device codes, Google and GitHub logins, sessions for agents without a browser.
- App review wants test credentials, but my app only had Google sign-in
I was one field away from submitting my MCP server to an app directory when I hit a wall I had not planned for: test credentials.
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 - Adding Google sign-in so non-developers can use your app
My site had exactly one way in: GitHub.
Yahhi✓ 0 - 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/authentication.md