veto
Related Servers
Alternatives to veto
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceEnables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.1418 npm14MIT
- AlicenseNot gradedqualityDmaintenanceUnified CLI multiplexer for AI coding agents, enabling orchestration of multiple coding CLI tools through a single interface with session persistence, cost tracking, and MCP tool support.7 npm19MIT
- FlicenseNot gradedqualityCmaintenanceAn autonomous AI development agent that enables full-stack coding, automated verification, RAG-powered code search, and quality assurance through MCP tools. Supports Gemini CLI, Claude Code CLI, with features like parallel verification, security scanning, and spec-driven development.5-
- AlicenseBqualityBmaintenanceMCP server that lets AI models invoke CLI agents (Gemini, Codex, Claude, OpenCode) as tools — with parallel execution, retries, and structured output parsing.12,405 PyPI4MIT
- AlicenseAqualityDmaintenanceOne MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.234MIT
- AlicenseNot gradedqualityAmaintenanceAutonomous spec-to-product coding-agent CLI. Its MCP server exposes 34 tools over stdio: project state and task-queue ops, memory retrieve/store, code search, quality and verification reports, repo hotspots/co-changes, and structured findings/learnings.13,919 npm1,100Business Source 1.1
TDQS
Scored across 93 tools
Several tool clusters have overlapping purposes: review pipelines (veto_code_review, veto_diff_review, veto_pr_review, veto_full_review, veto_pre_commit, veto_ci_gate) and status/dashboard tools (veto_status, veto_health, veto_metrics, veto_usage_status, veto_rate_status, veto_snapshot, veto_context_status, veto_autosave_status) are hard to distinguish at a glance. Memory/session tools are clearer, but the 93-tool surface produces many ambiguous pairs.
Nearly all tools use a consistent veto_ prefix with snake_case verb_noun or noun_action form (veto_memory_store, veto_session_save, veto_diff_review). Minor deviations exist, e.g. plural-noun prefixes (veto_plugins, veto_patterns_list, veto_secrets_scan) and bare acronyms (veto_adr, veto_rca), but the pattern is largely predictable.
93 tools is far beyond a well-scoped set and far exceeds the 50+ threshold for extreme mismatch. Many concerns could be consolidated into parameterized actions (e.g. one review tool with a mode flag), making this heavy surface a navigational burden.
The surface is remarkably broad, covering sessions, memory, council decisions, reviews, security, dependencies, docs, and learning — nearly every dev-assistant lifecycle stage. Gaps are minor rather than structural, though the sheer breadth makes some operations redundant rather than missing.