July 27, 2026 · 4 min read

Claude won't connect to ReminderIt? Fixes that work

If Claude will not connect to ReminderIt, the cause is usually one of a few simple things. A practical checklist that fixes it, ending with a whoami test.

A connection that will not take is frustrating, but with ReminderIt it is almost always one of a small handful of causes. Work through this checklist in order and you will usually be sorted in a couple of minutes, whether you use the hosted connector or a local Claude Desktop setup.

Check the connector URL

The single most common cause is a slightly wrong address. The ReminderIt connector URL is exactly https://mcp.reminderit.com. Open your client's connector settings and confirm it character for character, with no trailing path, no typo in the subdomain, and https rather than http.

A connector that points at the main site or the API host instead of the mcp subdomain will simply never hand Claude any tools. Correct the URL and the rest of this list usually falls into place.

Re-authorise through OAuth

The hosted connector signs you in through a secure OAuth consent screen rather than an API key. If the connection dropped, that approval may have lapsed or never completed. Remove the connector and add it again, then follow the consent screen all the way through until it returns you to Claude.

If a browser window opened and you closed it before approving, the connection stays half-made. Trigger the OAuth flow again and finish it, and a fresh per-client key is issued to your account automatically.

Confirm you are signed in, then refresh

OAuth can only link an account you are actually logged into. Make sure you are signed in to ReminderIt at reminderit.com in the same browser before you approve, so the consent screen has an account to attach to.

With the URL right and OAuth complete, refresh or reconnect the connector in your client so it re-fetches the tool list. A stale connector that was added while something was off often just needs this nudge to pick up all the tools.

If you use local Claude Desktop

A self-hosted setup connects differently, so the fixes differ. Open your claude_desktop_config.json and check the REMINDERIT_API_KEY value is a valid key that starts with rmt_, copied cleanly with no stray spaces or line breaks. Confirm REMINDERIT_API_URL points at https://api.reminderit.com.

After any edit to that file, fully restart Claude Desktop. The config is only read on startup, so a saved change does nothing until the client relaunches. If the key looks suspect, generate a fresh one in the dashboard at reminderit.com/api-keys.

Verify with whoami

Once it looks connected, prove it. Ask Claude "Who am I on ReminderIt?" and it runs the whoami tool. A reply naming your account means the link is live and authenticated end to end.

If whoami still fails after all of the above, revoke the connector's key at reminderit.com/api-keys and add the connector cleanly from scratch. Starting fresh clears out any half-finished authorisation that was quietly blocking you.