Your agent can build the integration.See the two prompts

One account. Every app.

Sign up once.
Zero setup for all your app logins.

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.

Your users see
Your app receivesNormalized identity
GET/v1/profile200 OK
{
  "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.

1 accountUnlimited apps
  • No provider developer accounts
  • No OAuth apps to create
  • No callback URLs to copy
  • No client secrets to juggle

One AnyOAuth account handles all of it.

After you sign up

Give your agent the skill.
It writes the login.

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.

01

Sign up once.

One AnyOAuth account covers every app. No provider accounts or OAuth apps.

02

Give your agent the skill.

Paste one prompt. The agent connects the AnyOAuth skill and MCP server. No JSON files.

03

Ask for login in any app.

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

Start with these two prompts.

Copy them into your agent. It installs the skill, connects MCP, and writes the login.

Step 1

Connect the skill and MCP server

Add the AnyOAuth skill with:
npx skills add AnyOAuth/anyoauth --skill anyoauth

Connect the AnyOAuth MCP server with:
npx anyoauth-mcp

Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and other MCP clients.

Step 2

Ask for the integration

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.

Your agent writes your login code.

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.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Gemini CLI
  • Windsurf
  • Cline
  • OpenCode
  • JetBrains
  • Zed
  • Neovim
  • Replit
  • v0
  • Codex
  • VS Code
  • Any MCP client

Secure by default.
Your app owns the session.

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 model
  • No provider tokens

    AnyOAuth returns a verified profile, not access to Google or GitHub APIs.

  • Browser-bound PKCE

    State and verifier stay tied to the browser that started the login.

  • Exact callbacks and one-time codes

    No open redirects. Codes are single-use and expire quickly.

  • Project-scoped identities

    Matching emails never merge accounts across apps.

The identity layer
for all your applications.

Use the same sign-in flow across every app you own. Leave provider-specific callbacks and profile formats to AnyOAuth.

One profile,
every provider.

A consistent response for the fields you need. Stable subjects keep identities separate within each project.

Googlegoogle subject
GitHubgithub subject
Your applicationprofile.subject

A token that
knows its limits.

Our token retrieves one profile. It expires in 15 minutes, can be revoked, and cannot access provider APIs.

AnyOAuth profile token
aop_••••••••••••••
Profile only15 minutesRevocable

Sessions that
stay yours.

You own the user record, session, and permissions. Get the identity, then continue with your application’s logic.

Verified identity
Your session

Zero password handling.
A clearer privacy boundary.

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 responsibilities

Identity data still needs protection. Social sign-in does not automatically make your website compliant.

Your identity provider

Handles the user’s credentials

AnyOAuth

Stores the normalized identity, not passwords

Your application

Owns sessions, permissions, and data use

Familiar accounts.
Across all your apps.

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.

Three steps.
One signed-in user.

One managed backend route. The same browser helpers in React, Vue, Astro, HTML and more.

  1. 1

    Mount your backend

    Configure your project credentials and mount the SDK router.

  2. 2

    Add your login buttons

    Call startLogin('google') or startLogin('github'). Cookies and callbacks are handled for you.

  3. 3

    Show the profile

    Read your signed-in user with getProfile(), then sign out with logout().

Read the quickstart
Your backend + frontendManaged SDK
// 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();

A few things
worth knowing.

Clear answers before you add another piece to your authentication stack.

Do I need a new account for every app?

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.

Do I need to register callback URLs or provider apps?

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.

Can my coding agent do the whole integration?

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.

Do I need a provider token?

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.

Does AnyOAuth manage my application sessions?

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.

What profile information is available?

Subject, provider, provider subject, name, username, email, email verification status, and avatar. Fields that a provider does not supply are returned as null.

How long does login last?

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.

Can I request inbox or repository access?

No. AnyOAuth is sign-in only. It requests identity scopes and does not provide access to repositories, messages, calendars, or other provider APIs.

Your next integration
is one prompt away.

Copy the prompt. Tell your agent which app. Review the result.