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.143 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.4 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-
- AlicenseBqualityAmaintenanceMCP server that lets AI models invoke CLI agents (Gemini, Codex, Claude, OpenCode) as tools — with parallel execution, retries, and structured output parsing.2022 PyPI4MIT
- AlicenseAqualityCmaintenanceOne 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.233MIT
- 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.1,179 npm1,068Business Source 1.1
TDQS
Scored across 93 tools
Many tools are differentiated by detailed descriptions, but large clusters overlap: code_review / diff_review / full_review / pre_commit / ci_gate / pr_review, plus multiple session, memory, agent, and learning operations. An agent can usually choose correctly with careful reading, but boundaries are not consistently crisp across 93 tools.
All tools share a veto_ prefix and mostly use snake_case, but the convention mixes verb_noun forms (veto_memory_store, veto_session_save) with noun-only names (veto_decisions, veto_workflow, veto_rca, veto_postmortem) and advisor/agent suffixes. It remains readable but is not a predictable verb_noun pattern throughout.
93 tools far exceeds the typical well-scoped MCP surface and creates an unwieldy, high-load set. Many specialized one-off advisors, generators, and workflows make the server hard to navigate as a cohesive toolkit.
The surface covers a remarkably broad domain: memory CRUD/export/import, sessions and handoffs, code/security/secrets review, dependency checks, git/PR/CI tooling, learning, agents, project mapping, and documentation. Minor lifecycle gaps exist, but most expected developer-assistant operations are represented.