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
- Account: your name, an optional email, your passkeys and recovery codes.
- App: one project you want to sign in to. It has a client ID, redirect URIs and, for apps with a backend, a client secret. Types:
web(has a server),spa(browser only, PKCE) andnative(mobile, desktop, CLI). - Agent connection: a coding agent you approved to manage your account over MCP.
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
- Your app redirects to
https://yourself.mees.sh/authorizewith its client ID, a PKCE challenge, state and nonce. - If you're not signed in to yourself, you confirm with your passkey. If the app isn't yours, it stops here.
- yourself redirects back with a single-use code, valid for 60 seconds.
- Your app's server exchanges the code at
/tokenand verifies the ID token signature. - Your app sets its own session cookie. The helper in each guide does all of this for you.
Endpoints
| What | URL |
|---|---|
| Discovery | https://yourself.mees.sh/.well-known/openid-configuration |
| Authorize | https://yourself.mees.sh/authorize |
| Token | https://yourself.mees.sh/token |
| User info | https://yourself.mees.sh/userinfo |
| Signing keys (JWKS) | https://yourself.mees.sh/.well-known/jwks.json |
| Revoke | https://yourself.mees.sh/revoke |
| Sign out everywhere | https://yourself.mees.sh/logout |
| Agent client registration | https://yourself.mees.sh/register |
| MCP | https://yourself.mees.sh/mcp |
Tokens
- ID token: ES256 JWT, 1 hour.
subis your stable account ID;audis the app's client ID.namewith theprofilescope,emailwithemail(alwaysemail_verified: false). - Access token: ES256 JWT with header
typ: at+jwt, 1 hour. Verify it in your own API with the JWKS andaud= client ID. - Refresh token: only with
offline_access, 30 days, rotated on every use.
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.