Skip to main content

How sign-in works

The connector uses OAuth. You never give your password or an API key to your AI app.
  1. You add the connector in your AI app. See the Quickstart.
  2. The app opens the WiseGuard sign-in page. Sign in with your WiseGuard account. New users go through checkout first.
  3. WiseGuard shows a consent page. It names the app and what it’s asking to do: manage your aliases, read your mail, and send mail as your aliases.
  4. You approve. The app gets an access token that only works with the WiseGuard connector.
Only apps WiseGuard has registered in advance can sign in. Today that’s Claude and Claude Code.

What you approve

The connector has four scopes. Each tool checks for its scope before it runs. wiseguard_whoami needs no scope. Any connected app can call it. With mail:read and mail:send, your agent can read the mail your aliases receive and send email as your aliases. See Security and privacy for how that’s kept safe. If the app calls a tool without the right scope, it gets a 403 with insufficient_scope. Reconnect and approve access to fix it. If you connected before the mail tools existed, your approval only covers aliases. The mail tools then get insufficient_scope. Remove the connector in the app, add it again, and approve the new access.

Plan requirement

You need a WiseGuard account to connect. New accounts go through checkout first, and a trial counts. Looking at your aliases and reading your mail is free. Changing aliases and sending email cost AI agent credits. Credits come with a paid plan. Trials don’t include them, so on a trial your agent can look but can’t make changes. Creating an alias also needs an active plan. If your account goes read-only, for example after a failed payment, the agent can’t create aliases. It can still make other changes with the credits you have left. When your plan ends, your credits expire. wiseguard_whoami tells your agent whether you can create aliases right now (canCreate), and how many credits you have left.

Disconnect and reconnect

To stop an app from using your account:
  1. In WiseGuard, open Settings → AI agents, choose the app and click Disconnect.
  2. Also remove the connector inside the AI app:
    • Claude: open Settings → Connectors and remove WiseGuard.
    • Claude Code: run claude mcp remove wiseguard.
Disconnecting in WiseGuard blocks the app right away. From then on, every request it makes gets a 403 with this message:
The app gets this with HTTP status 403 and error access_denied. To let the app back in, open Settings → AI agents in WiseGuard and click Reconnect. It works right away. If you also removed the connector in the app, add it again with the Quickstart steps.

What can go wrong

  • Sign-in loops or fails. Remove the connector in the app and add it again.
  • The app says it was disconnected. Reconnect it in Settings → AI agents.
  • Creating an alias fails with a plan error. Your plan is inactive. See Troubleshooting.
  • A change fails with a credits error. You’re out of credits, or on a trial. See Troubleshooting.
  • The mail tools fail with insufficient_scope. You connected before they existed. Remove the connector and add it again.