What MCP is, and how Claude uses it to call your phone

You can ask Claude to "call me at 8am to take my tablets" and your phone will actually ring at 8am. That small piece of magic runs on an open standard called the Model Context Protocol, or MCP. This piece explains what MCP is and how it lets Claude reach out of the chat and into the real world.

No deep technical background needed — the aim is to demystify what is happening when Claude schedules a call on your behalf.

What MCP actually is

On its own, a chat assistant can only talk. MCP is a standard way to give it hands: it defines how an assistant like Claude can discover and use external tools offered by a service. Think of it as a shared language between the assistant and the tools.

ReminderIt runs an MCP server that publishes a set of tools. When you connect it, Claude learns what those tools are called and what each one does, so it can pick the right one for what you ask.

Tools, not guesses

The important shift is that Claude is not pretending to set a reminder or writing it in a note it will forget. When you say "call me at 8am," Claude calls a specific tool — create_reminder — with structured details like the time, the message and the schedule.

That request goes to ReminderIt, which stores a real reminder on your account. The action is concrete and verifiable, which is why you can then ask "what reminders do I have?" and get an accurate list back.

The twenty-five ReminderIt tools

ReminderIt exposes twenty-five tools through MCP. For reminders there are tools such as create_reminder, update_reminder, list_reminders, list_upcoming, skip_next_occurrence and delete_reminder, plus test_call to ring you on demand.

Others cover voice — like list_voices and set_reminder_voice — and your account, such as get_usage for your remaining calls, get_recent_calls, and add_recipient for adding someone else with a consent call first. Each tool is a single, well-defined capability Claude can invoke.

From message to real phone call

Here is the full path. You type a request; Claude interprets it and, if it needs to, confirms your time zone, since ReminderIt schedules against IANA zones like Europe/London. Claude then calls create_reminder with the details, and ReminderIt saves a one-off (a specific date and time) or a recurring schedule (a cron expression such as 0 8 * * 1-5 for weekdays at 8am).

When that time arrives, ReminderIt places a real outbound phone call and reads your reminder aloud in a natural voice. If the call is missed, it can fall back to a WhatsApp message so the reminder still reaches you. The whole chain started with one sentence in the chat.

Why this is safe by design

MCP connections are scoped and revocable. When you connect Claude with the hosted connector, you sign in through OAuth and ReminderIt issues a per-client key you can revoke at reminderit.com/api-keys. Claude only ever operates inside your own account.

The design also protects other people: adding someone as a care-recipient triggers a consent call to them before ReminderIt will ring their phone. So the same protocol that lets Claude act on your behalf also keeps clear boundaries around whose phone can be called.