Sign up once.
One AnyOAuth account covers every app. No provider accounts or OAuth apps.
One account. Every app.
Your agent adds every login provider — Google, GitHub, and passwordless email — to every app. No provider developer accounts, OAuth apps, callback URLs, or client secrets.
Already have an account? Give your agent the skill and it writes the login for your next app.
{
"subject": "usr_demo_google",
"provider": "google",
"name": "Jane Smith",
"username": null,
"email": "jane@example.com",
"emailVerified": true,
"avatarUrl": "https://…"
}An AnyOAuth token. Profile access only.
Your agent writes the code between them.
Interactive preview. No sign-in request is sent.
One AnyOAuth account handles all of it.
After you sign up
After you create your AnyOAuth account, hand the skill and MCP server to your coding agent. It adds the provider buttons, callback route, token exchange, and session handling to each app. You don’t write provider-specific OAuth code or open a provider console.
One AnyOAuth account covers every app. No provider accounts or OAuth apps.
Paste one prompt. The agent connects the AnyOAuth skill and MCP server. No JSON files.
The agent creates or reuses a project, registers the exact callback, stores the secret on your backend, and writes the integration. Repeat for every app.
Quick start
Copy them into your agent. It installs the skill, connects MCP, and writes the login.
Add the AnyOAuth skill with:
npx skills add AnyOAuth/anyoauth --skill anyoauth
Connect the AnyOAuth MCP server with:
npx anyoauth-mcpWorks with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and other MCP clients.
Create AnyOAuth login for example.com using AnyOAuth. Enable Google, GitHub and Magic Email Link.Replace example.com with your app or domain. Your agent handles the rest.
It adds the provider buttons, callback route, token exchange, and session handling to your app. Your users choose Google, GitHub, or Magic Email Link.
Works with the agents and IDEs you already use.
Agent sign-in
AnyOAuth’s login services work for your agent as well as your users. Use Google or GitHub when a browser is available, or send a Magic Email Link to an inbox your agent can read.
Keep the session that started the login and open the link there. This is separate from the login code your agent writes for your app.
The agent writes the integration; AnyOAuth handles the identity boundary. Provider tokens stay out of your app, callbacks are exact, and credentials are short-lived.
Read the security modelAnyOAuth returns a verified profile, not access to Google or GitHub APIs.
State and verifier stay tied to the browser that started the login.
No open redirects. Codes are single-use and expire quickly.
Matching emails never merge accounts across apps.
Used by
SendHog, Chatic, and InstaX run on AnyOAuth in production. Each gets familiar sign-in across its product without managing a provider app for every launch.
“Do you work with small teams?”
Matched from your Services page ↗

Build someone
worth following.
Open any site to try the sign-in.
Use the same sign-in flow across every app you own. Leave provider-specific callbacks and profile formats to AnyOAuth.
A consistent response for the fields you need. Stable subjects keep identities separate within each project.
google subjectgithub subjectprofile.subjectOur token retrieves one profile. It expires in 15 minutes, can be revoked, and cannot access provider APIs.
aop_••••••••••••••You own the user record, session, and permissions. Get the identity, then continue with your application’s logic.
No passwords to collect, store, or reset. Let users sign in with their identity provider. AnyOAuth stores their profile, never their password.
Understand your data responsibilitiesIdentity data still needs protection. Social sign-in does not automatically make your website compliant.
Handles the user’s credentials
Stores the normalized identity, not passwords
Owns sessions, permissions, and data use
Give every app you own the sign-in options your users know. Manage them from one AnyOAuth account and get the same consistent profile format across providers.
Availability depends on the service’s configured provider applications. Profile fields vary by provider.
One managed backend route. The same browser helpers in React, Vue, Astro, HTML and more.
Configure your project credentials and mount the SDK router.
Call startLogin('google') or startLogin('github'). Cookies and callbacks are handled for you.
Read your signed-in user with getProfile(), then sign out with logout().
// Backend — configured with your project credentials
app.use("/auth", auth.router());
// Frontend — same helpers in your framework
anyoauth.startLogin("google");
const profile = await anyoauth.getProfile();
// On the sign-out button:
await anyoauth.logout();Clear answers before you add another piece to your authentication stack.
No. One AnyOAuth account covers unlimited apps. Your agent creates or reuses a project for each app, registers the callback, and keeps the client secret on the backend, so there is no account-per-app and no repeated provider setup.
No. Your agent reads the app, determines the exact callback, registers it with AnyOAuth, and writes the matching backend route. AnyOAuth manages the Google and GitHub applications, so you do not create provider apps or copy provider credentials.
Yes. Install the AnyOAuth skill and MCP server, then ask your agent to create AnyOAuth login for your app. It can inspect the project, create or reuse the AnyOAuth project, implement the login, store the secret, and run the checks. See the agent setup page for the two prompts.
No. The managed flow retrieves a verified profile through your backend. Provider tokens are not returned or stored. Existing code-based integrations still use an AnyOAuth profile-only token.
The managed SDK router can create and validate encrypted application cookies for you. You can also connect your existing session store. Your application owns user records and permissions.
Subject, provider, provider subject, name, username, email, email verification status, and avatar. Fields that a provider does not supply are returned as null.
Login attempts expire after ten minutes. Managed application sessions default to one day and can be configured. Legacy profile tokens expire after fifteen minutes and have no refresh flow.
No. AnyOAuth is sign-in only. It requests identity scopes and does not provide access to repositories, messages, calendars, or other provider APIs.
Copy the prompt. Tell your agent which app. Review the result.