mcp-progress
Related Servers
Alternatives to mcp-progress
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for Nova Agent progress reporting. Enables updating execution sessions and managing steps within tasks.-
- AlicenseAqualityBmaintenanceAsync MCP server for running long-running AI tasks with real-time progress monitoring, enabling users to start, monitor, and manage complex AI workflows across multiple models.636 npm5MIT
- AlicenseNot gradedqualityDmaintenanceAdds async processing to any MCP server, with timeout, task management, and subscription to task status via resources.2 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that sends webhook notifications to a configured URL, enabling AI assistants to notify users when long-running tasks complete.54 npm3-
- AlicenseCqualityDmaintenanceMCP server for sending notifications to ntfy.sh or self-hosted ntfy instances.212 npmMIT
- FlicenseNot gradedqualityBmaintenanceA lightweight MCP server that provides cross-project progress tracking tools (list, refresh, read, update, mark) for agents to query and manage work status across multiple tracked projects.-
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: notify sends a user notification, while start/update/complete handle the lifecycle of a progress operation. There is no overlap or ambiguity between them.
Three tools follow the verb_noun pattern (start_progress, update_progress, complete_progress), but notify is a bare verb without an object. This is a minor deviation from an otherwise consistent naming scheme.
Four tools is well-scoped for a progress-tracking server. Each tool serves a distinct purpose in the workflow, and the count feels neither too thin nor overloaded.
The progress lifecycle (start, update, complete) is covered, with an additional notify capability. A possible gap is the lack of an explicit cancel/abort operation, but the core workflow is complete enough for most use cases.