MIT
openclaw-task-mcp
Related Servers
Alternatives to openclaw-task-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Claude Code to interact with OpenClaw AI agents (Daemon, Soren, Ash, etc.) via the gateway API, providing tools to ask agents, list them, and check their status.3297 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.9 npm2MIT
- AlicenseBqualityDmaintenanceMCP server for ClickUp task management, enabling task search, creation, update, deletion, workspace info retrieval, and comment management via ClickUp API v2.1531 npmMIT
- AlicenseBqualityFmaintenanceMCP server that exposes OpenClaw Gateway tools to Claude Code and other MCP clients, enabling messaging, session management, scheduling, node control, web search, memory search, and TTS.216 npm14MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for managing Kaiten tasks through AI agents like Claude, enabling task retrieval, creation, updating, and time logging.14 npm2MIT
TDQS
B3.3/5.0
Scored across 3 tools
Disambiguation5/5
Each tool targets a distinct action: creating a task, listing tasks, and checking status. There is no overlap or ambiguity between purposes.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: start_task, list_tasks, get_task_status. The naming is uniform and predictable.
Tool Count5/5
Three tools is a well-scoped set for task lifecycle management. Each tool earns its place and there is no redundancy or bloat.
Completeness4/5
The core task lifecycle is covered: starting, listing, and retrieving status. A minor gap is the lack of an explicit cancel/abort operation, but the primary workflow works without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues