lauther-mcp
Related Servers
Alternatives to lauther-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityBmaintenanceEnables AI agents to reach users on their phone through push notifications, and to raise urgent, escalating alarms that fall back to a voice call until someone acknowledges. It also ships hooks that notify users automatically when Claude Code or Codex needs input or finishes a turn.321 npmMIT
@quirna/mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to request human approval before consequential actions, with policy-based routing, phone-based approver decisions, and signed audit evidence.40 npmMIT- AlicenseAqualityCmaintenanceEnables AI assistants to send push notifications and interactive alerts to iPhone and Mac devices via the BotBell app. It allows AI to receive user replies and manage notification bots for tasks like alerts, reminders, and remote approvals.26 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to send, update, and resolve live actionable notifications across Android, macOS, and the web, including asking questions and waiting for user replies. Supports targeting one device or all devices and syncing responses across devices.2 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to place outbound phone calls through the user's own Twilio account, delivering a spoken message or asking a single question and returning the recipient's transcribed reply to the agent. It exposes just two tools—one-way notifications and one-question calls to a fixed, preconfigured number with built-in rate limits and guardrails.35 PyPI1MIT

Hark MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents and MCP clients to send and update live notifications to one or all paired devices, ask the user a question, and wait for a response they tap or type on Android, macOS, or the web.163,865 npm2MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: ask_approval blocks for a yes/no decision, send_notification is fire-and-forget, get_location requests a one-shot position, and request_photo requests a one-shot image. The descriptions explicitly draw the approval-vs-notification boundary, so an agent cannot easily confuse them.
All four names follow a consistent verb_noun snake_case pattern (ask_approval, send_notification, get_location, request_photo). The verb variety is semantically motivated rather than arbitrary, and the pattern is perfectly predictable.
Four tools is a tight, well-scoped surface for a phone-based human-in-the-loop bridge. Every tool covers a genuinely distinct interaction type and none feels redundant or filler.
The surface covers the main human-interaction needs: permission, notification, location, and visual input. A minor gap is the absence of a way to ask a free-form question and get a text answer back, since ask_approval only returns APPROVED/DENIED/NO ANSWER.