This connector has been replaced by Reflecto.
Send notifications, ask approval questions, ring, remind and deliver files to your own paired phone.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 9 tools
Each tool targets a distinct action: scheduling vs cancelling reminders, pushing vs ringing a phone, sending vs receiving files/shared items, and requesting vs polling approvals. The only close pair, send_notification and remind_me, is clearly separated by immediacy vs future scheduling, and the descriptions reinforce the boundary.
All tool names follow a consistent snake_case verb_noun pattern: cancel_reminder, check_reply, get_shared_items, list_devices, request_approval, send_file, send_notification. Minor possessive forms like find_my_phone and remind_me still fit the imperative verb-first style without creating confusion.
Nine tools is well within the ideal range and each one earns its place in a personal-device integration server. The surface covers notifications, reminders, approvals, shared items, file delivery, device discovery, and phone location without redundant or filler tools.
Core workflows are covered: reminders can be scheduled and cancelled, approvals can be requested and polled, notifications can be sent, and shared items can be read incrementally. Minor gaps exist, such as no way to cancel a pending approval and no update mechanism for reminders, but these are workable and the server is explicitly stateless about some of them.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
list_devices2 fields changedOutput schema / properties / devices / items / properties / deviceIdAdded value: +{
+ "description": "Stable opaque id. Pass this as send_notification's `device` to reach exactly one device — labels are NOT unique, and a shared label delivers to every device that has it.",
+ "type": "string"
+}Output schema / properties / devices / items / requiredPrevious value: -[
- "label",
- "type",
- "reachable",
- "lastSeenAt"
-]New value: +[
+ "deviceId",
+ "label",
+ "type",
+ "reachable",
+ "lastSeenAt"
+]send_notification1 field changedInput schema / properties / device / descriptionPrevious value: -"Which devices to notify. Prefer the reliable values: 'all' (default), 'phone'/'mobile', or 'desktop'. A comma-separated list of custom device labels also works; call list_devices first to discover the exact labels (when that tool is available). An unknown label is skipped with a warning rather than failing — use the class names above unless the user named a specific device."New value: +"Which devices to notify. Prefer the reliable values: 'all' (default), 'phone'/'mobile', or 'desktop'. A comma-separated list of custom device labels also works; call list_devices first to discover the exact labels (when that tool is available). To reach EXACTLY one device, pass its `deviceId` from list_devices instead of its label — labels are not unique, and a label shared by two devices delivers to both. An unknown label is skipped with a warning rather than failing — use the class names above unless the user named a specific device."list_devices4 fields changedOutput schema / properties / devices / items / properties / lastSeenAt / descriptionPrevious value: -"Unix timestamp in seconds of last server contact"New value: +"Unix timestamp in seconds of last server contact. Coarse (hourly) for phones — prefer statusReportedAt for recency when present"Output schema / properties / devices / items / properties / onlineRemoved value: -{
- "type": "boolean"
-}Output schema / properties / devices / items / properties / reachableAdded value: +{
+ "description": "Whether the server has a delivery channel to the device right now. For a phone this means a live push registration — it can be reached, even if it is currently asleep or switched off. It does NOT mean the user is active on the device.",
+ "type": "boolean"
+}Output schema / properties / devices / items / requiredPrevious value: -[
- "label",
- "type",
- "online",
- "lastSeenAt"
-]New value: +[
+ "label",
+ "type",
+ "reachable",
+ "lastSeenAt"
+]cancel_remindercheck_replyfind_my_phoneget_shared_itemslist_devicesremind_merequest_approvalsend_filesend_notification
Add one secure layer between your agents and this server.