kata
Related Servers
Alternatives to kata
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables Codex CLI to delegate tasks to file-based specialized agents with isolated execution, auditability, and CI-friendly validation.4161MIT
- AlicenseNot gradedqualityAmaintenanceEnables reusable Markdown-defined coding agents—such as reviewers, test writers, or investigators—to be invoked from any MCP-compatible assistant and executed through a selected coding CLI, with results returned to the conversation.545 npmMIT
- AlicenseNot gradedqualityAmaintenanceLets you define reusable, task-specific coding agents in Markdown files and invoke them from any MCP-compatible client, running each one through a chosen coding CLI backend and returning the result to the same conversation. Supports shared backend and model settings, permission modes, and optional session continuity so an agent can continue work across multiple calls.545 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables coding agents to search, recommend, and validate a stack of reusable skills from a local catalog, producing deterministic plans without modifying the project.6,024 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables running reusable, task-specific coding agents defined in Markdown files from any MCP-compatible client, executing them with a chosen coding CLI backend and returning results to the same conversation. Supports configurable backends, models, permission levels, and session continuation for longer tasks.545 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables IDEs and coding agents to perform fast deterministic repository queries, symbol and dependency graph navigation, persistent memory recall, skill loading, security scanning, git inspection, and model routing with minimal token usage.MIT
TDQS
Scored across 5 tools
Each tool addresses a distinct stage of the chain lifecycle: listing, starting, advancing, saving, and exporting. There is no meaningful functional overlap between them.
All five tools follow the consistent verb_noun snake_case pattern: list_chains, run_chain, advance_chain, save_chain, export_chain. The naming is predictable and uniform.
Five tools tightly cover the core chain lifecycle without redundancy. This is a well-scoped size for a focused server.
The set covers listing, running, advancing, saving, and exporting chains, giving solid execution and authoring coverage. The main gap is the lack of an explicit delete/remove_chain operation, though save_chain can overwrite and this is a minor shortfall.