Simplepush MCP Server
OfficialRelated Servers
Alternatives to Simplepush MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI agents to send, receive, schedule, and manage SMS and MMS messages using the Twilio Programmable Messaging API. It provides comprehensive tools for handling bulk messaging, conversation threads, and real-time inbox monitoring through a secure, production-grade architecture.161MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to create and manage persistent task logs, decisions, dead ends, questions, and handoffs, with file staleness detection and activity reporting.1 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to communicate with humans using notify and ask semantics, supporting session management and blocking or non-blocking messages.19 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to communicate asynchronously via private inboxes and to ask a human a question and block until answered. Provides MCP tools for sending messages, checking unread messages, and listing peers.Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceField operations agent API for task management, geo-tracking, and team coordination. Built for African logistics, delivery, and field service teams.-
- AlicenseAqualityBmaintenanceLets AI agents send notifications, manage templates and read delivery status.133 npmMIT
TDQS
Scored across 14 tools
The core send/get/cancel tools are clearly separated by resource and action, but the retrieval tools—query_tasks, query_events, query_submissions, get_activity, and search_knowledge—overlap in scope and rely heavily on their detailed descriptions to keep an agent from picking the wrong one.
All tool names follow a consistent snake_case verb_noun pattern, with parallel names for parallel resources such as get_task_answer and get_notification_answer. There are no mixed conventions or vague generic verbs.
Fourteen tools cover the domain well: sending tasks and notifications, managing subtasks, retrieving answers, querying statuses and events, searching knowledge, and downloading attachments. Each tool maps to a distinct workflow without the set feeling bloated.
The lifecycle is broadly complete: create, append, cancel, read, list, search, and download are all represented. Minor gaps remain, such as no direct full read of a sent notification and no update path for already-sent tasks, but these are outside the core workflow's critical path.