Alarms
Set an explicitly requested one-shot alarm on your iPhone and understand permissions, timing, and delivery results.
Use an alarm when you explicitly want an urgent reminder on your linked iPhone. Agent Alerts sends a push command, then the iPhone uses AlarmKit to schedule a one-shot alarm.
Before you start
- Use an iPhone running iOS 26 or later and sign in to Agent Alerts.
- In Agent Alerts Settings, choose Enable Alarms and approve the system permission. The app offers alarm setup as a Pro feature.
- Keep notification permission and device registration working so the phone can receive the command.
- Connect your AI client through remote MCP. A publishing-token connection needs the
send_alarmscope; ordinary publishing access alone does not grant alarm access.
Ask your agent to check Agent Alerts status if the account or device connection is uncertain. A registered device is not proof that alarm permission is enabled.
Ask for one alarm
For example:
Set one Agent Alerts alarm on my linked iPhone in 10 minutes titled “Take a break”. Tell me whether the push was accepted. I will check the alarm on my phone.
For an exact clock time, include the date and time zone. The native MCP tool is agentalerts_alarm. This example shows its arguments, not webhook or CLI syntax:
{
"title": "Take a break",
"fireInSeconds": 600,
"alarmId": "break-reminder-001"
}
Choose exactly one schedule:
fireInSeconds: a positive whole number. The relative countdown starts when the phone processes the command, so network or background-processing delays can move the alarm later.fireAt: an ISO 8601 date and time with a time-zone offset. Prefer this for a specific clock time.
The title can be up to 40 characters. An optional alarmId of up to 80 characters helps the phone suppress duplicate commands. Reuse it only for the same alarm; use a new ID for a different alarm. It is not an edit or cancellation handle.
Optional alertTitle and alertBody customize the notification accompanying the command. deepLink opens supporting context when the alarm is tapped in Recent Alerts. deviceInstallId targets one known linked iPhone; project metadata only organizes the alert.
Alarm, notification, or Live Activity?
- An alarm asks the phone to schedule an AlarmKit alarm. Use it only when the user requested an alarm.
- A notification delivers a visible message through iOS notifications. It does not schedule an alarm.
- A Live Activity keeps ongoing information visible on the Lock Screen or Dynamic Island. Scheduling a future Live Activity does not schedule an alarm.
An alarm command may also show a delivery notification. Even if its text says the alarm was scheduled, verify the phone's actual alarm state. The alarm tool does not create or update an Agent Alerts Live Activity.
Check the result
sent: APNs accepted the command for the reported targets.partial: APNs accepted it for some targets, but others failed.no_targets: no matching registered device was available.failed: delivery failed for the attempted targets.
These are transport results. They do not confirm that the phone scheduled, displayed, or sounded the alarm. In Agent Alerts Settings, device diagnostics include the last alarm result and when it was handled.
Limits and troubleshooting
The current MCP catalog has no standalone alarm status or cancellation tool. Its scheduled Live Activity status and cancellation tools apply only to scheduled Live Activities. Recurring alarms are not part of this one-shot tool.
If you see Alarm scope required, use a connection approved for alarm access. If you get no_targets, open Agent Alerts, check the account and device registration, and confirm alarm and notification permissions before trying again.
If the push was accepted but no alarm appears, check the phone's last alarm diagnostic and system permission. Do not repeatedly send new IDs while the outcome is uncertain. A timestamp already in the past may be scheduled almost immediately when the phone handles it; choose future times with enough delivery margin.
Use a directly configured device alarm for a time-critical reminder you cannot afford to miss. Remote delivery and background processing are not guaranteed. For ordinary updates, see notifications.