io.github.koten-ai/zeus-dev-helper
OfficialRelated Servers
Alternatives to io.github.koten-ai/zeus-dev-helper
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceLocal-first Agent OS that wraps Claude Code, Codex CLI, and other coding agents in a replayable Seed → Ledger → Runtime contract, driven by an interview → seed → execute → evaluate → evolve workflow loop.3431,487 PyPI6,071MIT
- FlicenseAqualityCmaintenanceEnables coding agents to design first by interviewing users, refining specs in digestible chunks, producing bite-sized TDD plans, and autonomously executing them through subagents with a server-verified red/green testing gate.11-
- AlicenseNot gradedqualityAmaintenanceEnables evidence-gated, multi-session AI coding runs with plan-build-ship state management, coordinating Claude Code and Codex native agents.10 npmMIT

Planwrightofficial
FlicenseNot gradedqualityDmaintenanceEnables orchestration of autonomous coding agents (Claude Code, Cursor, etc.) through an objective-native planning board with hash-chained audit trail. Humans define outcomes, agents claim and execute tasks via MCP.7-- AlicenseNot gradedqualityFmaintenanceEnables AI agents to autonomously request services from other specialized agents and compensate them via x402 micropayments. Demonstrates a Machine-to-Machine economy using A2A protocol for agent communication, MCP for context management, and blockchain-based payments on Base network.32 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents to plan, build, and review websites and product interfaces with a persistent, user-led process, including design direction, component contracts, and implementation review.-
TDQS
Scored across 12 tools
There is some overlap between smoke_test_agent and smoke_test_zeus, and between doctor and readiness_check, which could confuse an agent. However, other tools like bind_contract, scaffold_app, and use_sample have distinct purposes, so the ambiguity is limited.
The naming is a mix of verb_noun patterns (e.g., smoke_test_agent, readiness_check) and bare verbs (doctor, next_step). While most use snake_case, the inconsistency between using 'check' in readiness_check and 'doctor' for health might cause minor confusion.
With 12 tools, the count is within the typical well-scoped range for a complex developer assistant. Each tool addresses a different aspect of the development workflow, though the number feels slightly high but not problematic.
The set covers the core lifecycle of starting, configuring, and verifying a project, but lacks tools for explicit update or deletion of configuration or samples. Some workflows might require manual steps outside the toolset, creating minor gaps.