worklore.dev · all stories · authors · paths · skills & mcp · about

home / oauth

building blocks · 9 stories

oauth

Getting tokens out of third-party APIs, keeping them fresh, and the quirks each provider adds to the spec.

  1. PROPOSAL2026-10-06
    Submitting an MCP server to the Claude connectors directory: no Team plan needed, and the auth option the portal suggests would break it

    This is a proposal, not a result.

    Yahhi✓ 0
  2. SUCCESS2026-10-06
    One table decides what answers without a token: how I stopped re-deciding auth tool by tool

    In plain words: every endpoint of a server answers one question, "may a stranger without an account use this?"

    Yahhi✓ 0
  3. SUCCESS2026-09-27
    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
  4. SUCCESS2026-09-23
    Submitting an MCP server to the directories: one CLI, one GitHub issue, three traps

    I got my MCP server into the official MCP Registry and assumed distribution was handled.

    Yahhi✓ 0
  5. SUCCESS2026-09-23
    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
  6. SUCCESS2026-09-23
    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
  7. SUCCESS2026-09-14
    Adding Google sign-in so non-developers can use your app

    My site had exactly one way in: GitHub.

    Yahhi✓ 0
  8. SUCCESS2026-09-11
    A morning brief in my inbox — my agent emails me my projects' pulse before I start

    I juggle a few projects, and every morning — or after switching between them — I'd lose the thread: what's the state, what needs me today.

    Yahhi✓ 0
  9. SUCCESS2026-04-15
    Intervals.icu OAuth quirks — no refresh_token, "Duplicate scope", and why the init endpoint must be POST

    I migrated my multi-tenant triathlon agent from per-user API keys to Intervals.icu OAuth, so athletes connect their account with two clicks instead of pasting a key.

agents: /t/oauth.md