How it works

yourself is an OpenID Connect provider where every app has exactly one possible user: the account that created it. You sign in with a passkey once; after that, your apps sign you in with a redirect.

The pieces

Quick start

Paste this to your coding agent from inside the project that needs sign-in:

Prompt
Connect to my yourself server and use it for sign-in in this project.

1. Add the MCP server:
   claude mcp add --transport http yourself https://yourself.mees.sh/mcp
2. Install the skill:
   mkdir -p ~/.claude/skills/yourself && curl -fsSL https://yourself.mees.sh/skill.md -o ~/.claude/skills/yourself/SKILL.md
3. Run /mcp, pick "yourself" and authenticate (I'll approve in the browser).
4. Add sign-in to this app with the yourself tools so only I can use it.

A sign-in, step by step

  1. Your app redirects to https://yourself.mees.sh/authorize with its client ID, a PKCE challenge, state and nonce.
  2. If you're not signed in to yourself, you confirm with your passkey. If the app isn't yours, it stops here.
  3. yourself redirects back with a single-use code, valid for 60 seconds.
  4. Your app's server exchanges the code at /token and verifies the ID token signature.
  5. Your app sets its own session cookie. The helper in each guide does all of this for you.

Endpoints

WhatURL
Discoveryhttps://yourself.mees.sh/.well-known/openid-configuration
Authorizehttps://yourself.mees.sh/authorize
Tokenhttps://yourself.mees.sh/token
User infohttps://yourself.mees.sh/userinfo
Signing keys (JWKS)https://yourself.mees.sh/.well-known/jwks.json
Revokehttps://yourself.mees.sh/revoke
Sign out everywherehttps://yourself.mees.sh/logout
Agent client registrationhttps://yourself.mees.sh/register
MCPhttps://yourself.mees.sh/mcp

Tokens

Development URLs

Redirect URIs must be https, except http://localhost and http://127.0.0.1, which match on any port. Register both your dev and production callback; agents can add more later with update_app.