July 27, 2026 · 4 min read

How the Claude and ReminderIt OAuth login works

A plain-English walk through the ReminderIt OAuth screen in Claude: what you approve, the key it quietly creates, and how to revoke access anytime.

Connecting Claude to ReminderIt takes one sign-in and no copied secrets, thanks to OAuth. But it is fair to want to know exactly what you are agreeing to before you click Approve.

Here is what that consent screen does, what it creates in your account, and where the off switch lives.

What OAuth is doing here

When you add the ReminderIt connector at https://mcp.reminderit.com, your client sends you to a ReminderIt-hosted sign-in page. You log in to ReminderIt there, not inside Claude, so Claude never sees your ReminderIt password.

OAuth is simply the handshake that lets you grant Claude access to your account without handing over your credentials. You stay in control of the grant, and you can withdraw it later.

What the consent screen approves

The screen asks whether you want to let this client act on your ReminderIt account. Approving means Claude can use the ReminderIt tools on your behalf: creating and editing reminder calls, listing what is scheduled, checking your usage, and placing a test call.

It is scoped to your account only. Claude cannot see other people's reminders, and it cannot reach anything outside ReminderIt through this grant.

The per-client key created behind the scenes

When you approve, ReminderIt generates a per-client API key tied to that specific connection and stores it for you. You never have to copy or paste it; it is the credential Claude uses quietly on each request.

Because each client gets its own key, you can revoke one without disturbing the others. Connect Claude on two machines and each has a separate key you can pull independently.

Example: your first request after signing in

Once the connector is authorised, try "Who am I signed in as on ReminderIt?" Claude calls whoami and reads back your account, which confirms the grant landed on the right login.

Then "List my active reminders" runs list_reminders. If it returns your reminders (or an empty list on a fresh account) with no auth error, the OAuth connection is healthy and you are ready to create your first call.

Revoking access at reminderit.com/api-keys

Every grant shows up at reminderit.com/api-keys as its own entry. To disconnect Claude, revoke that key; access stops immediately and your reminders stay exactly as they were.

This is the clean way to remove a device you no longer use, or to reset a connection that is misbehaving before authorising a fresh one.