ReminderStream in your assistant
Use an MCP-compatible assistant to manage reminders and, with separate permissions, contacts and notification preferences. Gmail is optional. You do not need to connect a mailbox or enable SMS to manage reminders.
Early access
A custom connector is different from an Anthropic directory listing. We have not claimed directory approval or completed every live-client and unattended-workflow check. Tool availability depends on the deployed release and the permissions you grant. Provider delivery and calendar copies have separate limits.
Connect Claude
- Create your ReminderStream account and complete the initial policy and AI-processing acceptance. Existing saved acceptance remains valid.
- In Claude, open Customize → Connectors and add a custom connector. Enter
https://mcp.reminderstream.com. Available menus and administrator controls depend on your plan and Claude experience. - Use OAuth sign-in. Do not paste your password, API key or machine-client secret into a conversation. Review the app name, return destination, account and requested permissions on our connection screen.
- Approve only the access you intend. Enable the connector in your conversation. Ask for a small date range first, then review any proposed changes.
Other compatible clients may use https://mcp.reminderstream.com/mcp. These are separate OAuth resource URLs: keep the exact URL you connected with. Claude Code uses its own sign-in and a local callback; a machine-to-machine token is not a replacement for Claude user sign-in.
Permissions stay under your control
- reminderstream/read: Read reminders, inspect their notification status, and analyze submitted text. Analysis uses AI allowance and saves derived suggestions, not the original text.
- reminderstream/write: Create, edit, complete, cancel, reopen and snooze reminders. Changes can schedule or cancel notifications.
- reminderstream/settings.read: Read notification preferences, contact schedules and usage allowances.
- reminderstream/settings.write: Change notification preferences and contact schedules. Verification, consent and STOP restrictions still apply.
- reminderstream/contacts.read: Read your saved contact methods and their verification and consent status.
- reminderstream/contacts.write: Add pending contact methods, enable or disable verified contacts with existing consent, and remove contacts. Verification and new consent require the website.
- reminderstream/history.read: Read derived communication results and linked reminders. No mailbox or original-message access.
- offline_access: Refresh this connection within its fixed 30-day lifetime. Revoke it at any time in Settings.
An older reminder-only connection does not gain contacts or settings access automatically. Reconnect and review the additional permissions when needed. The assistant cannot accept consent, verify ownership, undo STOP, change sign-in settings, create credentials or delete your account.
What the tools do
| Area | Tools |
|---|---|
| Reminders | extract_reminders, create_reminders, list_reminders, get_reminder, update_reminder, complete_reminder, cancel_reminder, reopen_reminder, snooze_reminder |
| Delivery and calendar | get_reminder_notifications, get_calendar_handoff |
| Preferences and usage | get_settings, get_usage, update_notification_settings, update_contact_schedule |
| Contacts | list_contacts, add_contact, update_contact, remove_contact |
| Derived history | list_communications |
Despite its name, create_reminders saves one event per call. Extraction saves derived suggestions and uses AI allowance; it does not itself save reminder events or retain the original submitted text. A duplicate may return an existing reminder instead of creating one. The assistant should explain which occurred.
Try these requests
- “Show my reminders from January 4 through January 10, 2027, including their time zones.”
- “Create a weekly recycling reminder every Wednesday at 3:30 PM America/Chicago, starting January 6, 2027.”
- “Show the planned alerts for my recycling reminder, then help me change its time to 4 PM after I review it.”
- “Show my contact methods and their verification status. Help me add a new email, and show me where to verify it.”
- “Show my current reminder settings. Propose a 7 AM morning brief and wait while I review the change.”
Weekly events and limits
Choose a weekday and an optional local time. Weekly events appear in the occurrence-day morning brief and the enabled one-hour-before alert for timed events. Advance 7-day, 5-day, day-before and other offsets do not apply. Done advances one occurrence; Cancel stops the series. Reopen resumes at the next matching weekday. Weekly events cannot be snoozed; edit their time instead.
Save up to ten events per event-local date; completed and canceled events count. SMS uses a shared allowance of 120 logical messages in a rolling 30 days and up to three reminder notices per number per local day. Verification and service replies also use the shared allowance; provider-managed replies are separate. Organized reminder SMS can use up to five carrier segments; segments can be billed separately. Enabled, verified recipients and saved consent are still required. Quiet hours, STOP and eligible email fallback apply.
Contacts and delivery
An account supports up to ten phone numbers including any main phone; pending and disabled numbers count. Five additional emails are allowed separately. There is no arbitrary SMS-send tool. Creating or managing events can schedule notifications to eligible verified, consented recipients. Adding a contact makes it pending and unverified. This tool does not send a code. The person must complete ownership verification and any new SMS consent in Settings. Enabling a contact requires existing verification and consent; an assistant cannot override STOP. Removing a contact stops its future delivery but does not cancel saved events.
Pending means scheduled work remains. Submitted means handed to the provider, not confirmed handset or inbox delivery. Old event-version jobs may be suppressed. Calendar handoff opens the signed-in website; saved calendar copies do not synchronize with later changes.
Troubleshooting
- Permission required: reconnect with the named permission. Existing grants do not expand themselves.
- Connection expired: reconnect after the fixed 30-day grant ends. Access tokens can refresh within that period. Revoke a connection in Settings whenever you want.
- Event or schedule changed: read the current event version or settings revision, review the new state, then make a fresh decision. Do not blindly retry a mutation.
- Uncertain save: inspect the current events before retrying. Reuse extraction source/item identifiers or the same create idempotency key; a reused key with different content is rejected. Create-key replay is bounded to 24 hours.
- No alert: inspect the event’s notification history, recipient readiness, quiet hours, suppression and allowances. A scheduled job does not prove delivery.
Optional email and nightly workflows
Gmail access belongs to the assistant provider’s Gmail connector. Submit only selected content needed for reminders. ReminderStream does not connect to your Gmail mailbox or request Claude’s conversation history, memory or files. See the cloud workflow guide for the separate setup. A task waiting for permission or an expired connection is blocked, not a successful run. Real computer-off acceptance for our integration remains incomplete.
Claude requirements checked November 3, 2026: authentication, connector checklist, and directory submission. Menus and availability can change.