notify-human-mcp
Related Servers
Alternatives to notify-human-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to request user decisions and send notifications via Discord when human intervention is required during autonomous tasks. It supports blocking questions with custom options, progress reporting, and persistent state for seamless remote task management.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to send messages and rich embeds to Discord via webhooks, supporting plain text messages, formatted embeds with images and fields, and customizable webhook appearance for AI-powered Discord notifications and integrations.8 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to send messages to human users via chat platforms (currently Discord) and optionally wait for human responses, facilitating human-in-the-loop interactions.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI models to send plain text messages, formatted release announcements, and teaser previews to Discord channels using webhooks. It provides secure local webhook management and supports rich embeds with customizable styles for automated notifications.153 npm-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to send notifications to Discord channels via webhooks when tasks complete, errors occur, or user intervention is needed. Deployed serverlessly on Cloudflare Workers with support for rich message formatting and embeds.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to send text messages and images to Discord channels via webhooks.13 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose (send a notification to the human) is stated unambiguously.
A single tool named 'send' is a clear, conventional verb. With only one tool there is no inconsistent pattern to violate.
For a narrowly scoped server whose sole job is pinging a human, one tool is the right shape rather than a thin surface. It is minimal but not under-built for the stated purpose.
The send tool fully covers the core lifecycle of a fire-and-forget notification (status, ask, formatting, length limits), and no create/update/delete cycle is needed. Minor gaps exist, such as no channel configuration or acknowledgement/read-status retrieval.