alabasta
Related Servers
Alternatives to alabasta
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to interact with ClawWork task management, allowing them to access task feeds, claim and complete tasks, post comments, and submit artifacts.31 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to claim task cards from a self-hosted board, receive complete briefings, and submit handoffs with evidence and telemetry for human validation.-
- AlicenseAqualityAmaintenanceEnables agents to delegate tasks to human/AI workers on TaskMarket by listing, inspecting, and submitting work, while leaving spending flows to the user-authorized CLI.99 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to pick up, park, and hand off work on a shared task board with a DAG of work.MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to receive and act on voice-captured tasks delivered as GitHub issues, including retrieving full context, adding notes, asking the developer questions, and closing tasks when complete.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to securely read, update, and create tasks on ProjectFlow boards.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct action in the task workflow: reading, listing, starting work, gathering context, submitting a resolution, moving to review, and reporting blockers. No two tools overlap in purpose; even submit vs mark-ready are differentiated by whether a resolution is included.
All tools follow the consistent pattern alabasta_<verb>_<object> using snake_case. Verbs are specific and descriptive (get, list, start, collect, submit, mark, report), and objects clarify the target (task, git_context, resolution).
Seven tools is well within the ideal 3-15 range and each tool serves a necessary step in the workflow. The count is neither bloated nor sparse, and each tool has a clear role without redundancy.
The tool set covers the full lifecycle of task work: retrieve, list, begin, gather supporting context, submit outcome, escalate for review, or report a blocker. No critical workflow step is missing; the human-in-the-loop acceptance is intentionally outside the agent's scope but the agent has all needed actions to complete and hand off.