Where to find your ReminderIt API key for Claude

If you are wiring ReminderIt into Claude, you may be hunting for an API key. The honest answer is that most people never need to touch one. Whether you do depends on how you connect.

This guide shows you where the key lives, what it looks like, the one scenario that actually requires it, and how to pull it back the moment you change your mind.

The short answer: Dashboard, then API Keys

Sign in at reminderit.com and open the API Keys section of your dashboard. That is the single place keys are created, listed, and revoked. You can reach it directly at reminderit.com/api-keys.

Keys are strings that begin with rmt_ followed by a long random tail. Treat one like a password: anyone holding it can act on your ReminderIt account until you revoke it.

When Claude actually needs a key

You need a key only for a local or self-hosted setup, such as running the ReminderIt MCP server inside Claude Desktop's own configuration file. In that arrangement your machine talks to the ReminderIt API directly, so it has to authenticate with a key you paste in.

That is the exception, not the rule. If you are using Claude on the web or in a client that supports custom connectors, you almost certainly do not need to copy anything.

When you do not need a key at all

The recommended route is the hosted remote connector. In your client's connector settings you add a custom connector pointing at https://mcp.reminderit.com and sign in once through a secure OAuth screen. No key is copied by hand.

Behind the scenes that flow still creates a per-client key in your account, but ReminderIt manages it for you. You can see and revoke it later at reminderit.com/api-keys, which is handy if you ever want to cut off one specific client.

Example: putting a key into a local Claude Desktop setup

Install the server with pip install reminderit-mcp, then add a reminderit entry to Claude Desktop's config with your key in the REMINDERIT_API_KEY environment variable and https://api.reminderit.com as the API URL. Restart the client so it picks up the change.

Once it reconnects, test it in plain language: "Ring my phone right now to check the connection." Claude calls test_call, and your phone rings. Follow up with "What reminders do I have?" to confirm list_reminders is returning your data. If both work, the key is wired in correctly.

Revoking a key whenever you like

Every key can be revoked from reminderit.com/api-keys. Revoking is instant and it does not delete your reminders; it simply stops that key, and whichever client was using it, from reaching your account.

If you ever suspect a key has leaked, or you are retiring an old machine, revoke first and generate a fresh one for anything that still needs access.