ReminderIt

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 聊天与邮件

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://mcp.reminderit.com/mcp

claude mcp add --transport http reminderit https://mcp.reminderit.com/mcp

{
  "mcpServers": {
    "reminderit": {
      "url": "https://mcp.reminderit.com/mcp"
    }
  }
}

{
  "servers": {
    "reminderit": {
      "type": "http",
      "url": "https://mcp.reminderit.com/mcp"
    }
  }
}

https://mcp.reminderit.com/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月8日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• list_reminders

  List every reminder on the account with its schedule, state and next call time. Start here for almost any request about existing reminders — it is the only way to discover reminder IDs, which every other reminder tool needs. Paused reminders show WHY they are paused (out_of_credi

• get_reminder

  Get the full configuration of one reminder as JSON. Use when you need detail that list_reminders omits — the exact spoken message, cron expression, skip dates, channel toggles, or voice override. Also use this to read current values before a partial update, so you don't overwrite

• list_upcoming

  Show the next scheduled calls across ALL reminders, in chronological order. Answers "what's coming up?" better than list_reminders, because it expands recurring rules into actual upcoming occurrences and merges them into one timeline. Args: limit: How many upcoming occurrences to

• get_recent_calls

  Show recent delivery history — what was actually called, sent, or missed. Use this to answer "did it call me?", "why didn't I get it?", or to confirm a reminder is really firing. Statuses: completed/answered = the person picked up; no-answer/busy = rang but nobody answered (a Wha

• create_reminder

  Schedule a new reminder phone call. This places REAL calls, so get the schedule right the first time: resolve the timezone via whoami, and read the result back to the user afterwards. Provide exactly one schedule: run_at (one-off), cron_expr, or interval_days. Leave the voice arg

• update_reminder

  Edit a reminder's wording or schedule. Only the fields you pass are changed. Use for "move it to 7am", "say it differently", "stop after the 20th". To pause or resume, use pause_reminder / resume_reminder. To change the voice, use set_reminder_voice. To skip particular dates, use

• set_reminder_voice

  Give one reminder its own voice, overriding the account default. Use when a specific reminder should sound different — a calm, slower voice for medication; an energetic one for a workout; a different language for a relative. Call list_voices first to get valid voice IDs, and prev

• clear_reminder_voice

  Remove a reminder's custom voice so it uses the account default again. Args: reminder_id: Reminder whose voice override should be cleared.

• set_reminder_channels

  Choose what happens when a reminder call isn't answered. The phone call itself is always attempted. These toggles control the follow-ups: WhatsApp is on by default, email is off. Note each delivered fallback also consumes one call from the account's quota. Args: reminder_id: Remi

• set_skip_dates

  Set the specific dates a recurring reminder should NOT call. The right way to handle holidays, travel, or a pause of a few days — far better than deleting a reminder and rebuilding it. This REPLACES the existing skip list, so include dates the user still wants skipped (read them

• pause_reminder

  Pause a reminder so it stops calling, keeping all its settings intact. Prefer this over delete_reminder whenever the user might want it back — it is fully reversible with resume_reminder. Args: reminder_id: Reminder to pause (from list_reminders).

• resume_reminder

  Resume a paused reminder so it starts calling on its schedule again. If it was paused automatically for out_of_credit and the account still has no calls left, it will pause again at the next occurrence — check get_usage and tell the user. Args: reminder_id: Reminder to resume (fr

• skip_next_occurrence

  Skip only the next scheduled call, leaving the rest of the schedule untouched. Use for "not tomorrow, but keep it going after that". To skip particular calendar dates instead, use set_skip_dates. Args: reminder_id: Reminder whose next call should be skipped.

• test_call

  Place an immediate test call for a reminder so the user can hear it right now. The phone will ring within seconds — only do this when the user has asked to test, and never repeatedly. It consumes one call from their quota and does not change the schedule. Args: reminder_id: Remin

• delete_reminder

  Permanently delete a reminder. This cannot be undone. Confirm with the user first, quoting the reminder's title and schedule. If they may want it later, use pause_reminder instead. Args: reminder_id: Reminder to delete (from list_reminders).

• list_voices

  List the voices available on this account, with language, accent and tier. Call before set_voice_settings or set_reminder_voice to get valid voice IDs — never guess one. Voices marked premium may not be included in every plan; if the account's plan doesn't include one, calls fall

• get_voice_settings

  Show the account's default voice — the voice every reminder uses unless overridden. Read this before changing anything, so you can report what actually changed and leave unrelated settings alone.

• set_voice_settings

  Change the account's DEFAULT voice, affecting every reminder without an override. For a single reminder only, use set_reminder_voice instead. Get valid IDs from list_voices; preview_voice lets the user hear one first. Args: voice_id: Voice ID from list_voices. personality: "gentl

• preview_voice

  Generate a short audio sample of a voice so the user can hear it before choosing. Returns a URL to the generated audio. Useful when a user is deciding between voices, or wants to check how their own reminder wording will sound. Args: voice_id: Voice ID from list_voices. text: Wor

• whoami

  Identify the connected ReminderIt account: who it is, their timezone, plan and quota. Two jobs. First, it is the connection check — call it when the user asks "am I connected?", "which account is this?", or when another tool returns an auth error, to confirm the API key is valid

• get_usage

  Get remaining call quota, calls used, plan, and the current billing period. Check before creating several reminders or suggesting a test call, and whenever a delivery fails unexpectedly. One call OR one WhatsApp fallback each consume one unit from the same pool. When the balance

• list_recipients

  List care-recipients — other people this account can send reminders to. Needed to get the recipient_id for create_reminder. Consent status matters: only "confirmed" recipients receive calls; "pending" means they haven't accepted the verification call yet, so reminders to them wil

• add_recipient

  Add another person who can receive reminder calls, e.g. an elderly parent. ReminderIt immediately places a consent verification call to the number; reminders are only delivered after that person accepts. Only add someone the user genuinely has permission to call, and confirm the

• resend_recipient_verification

  Re-send the consent verification call to a recipient who hasn't confirmed yet. Use when list_recipients shows consent as pending and the person missed the first call. Don't repeat it more than necessary — each attempt rings their phone. Args: recipient_id: Recipient to re-verify

• remove_recipient

  Remove a care-recipient from the account. Any reminders targeting them will stop being delivered. Confirm with the user first. Args: recipient_id: Recipient to remove (from list_recipients).

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（reminderit.com）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 1109 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 25 个工具描述，未发现针对 AI 的隐藏指令

与“聊天与邮件”中的其他服务器比较i

• 星标数多于此分类中其他 1861 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1861 个服务器的 41% 更新
• 基础检查结果等于或优于此分类中其他 1861 个服务器的 46%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README