Veto
@jigyasudham
About Veto
93 agentic MCP tools + 49 specialist agents for every major AI CLI. Self-learning, no API keys.
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"veto": {
"command": "npx",
"args": [
"-y",
"--package",
"@jigyasudham/veto",
"veto-server"
]
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Veto?
Veto is a local MCP server that gives every major AI CLI — Claude Code, Codex, Gemini, Cursor, Windsurf, Zed, JetBrains — a shared layer of 93 agentic tools and 49 specialist agents. It’s designed for developers and teams who want deterministic, guardrailed tooling across multiple AI assistants.
How to use Veto?
Install via npx @jigyasudham/veto init. On a subscription there is no extra token cost and no API key required; on pay-per-token billing, optional LLM calls count toward usage and Veto warns you if it detects an API key.
Key features of Veto
- 49 specialist agents across 6 domains plus a 7-agent Council.
- Deterministic-first agents run as real expert modules at zero token cost.
- Guardrails that catch the AI's own mistakes (dependency hallucination, decision drift, compounding-error circuit breaker).
- Cross-CLI memory to save sessions in one tool and resume in another.
- Self-learning router that re-tunes its thresholds over time.
- CI gates and secrets scanning.
Use cases of Veto
- Use 42 deterministic worker agents for development, security, memory, research, quality, and workflow tasks.
- Let the Council agent debate trade-offs before building features.
- Save a session in one AI CLI and resume it in another with full context intact.
- Apply guardrails to catch hallucinated dependencies and prevent compounding errors during complex coding sessions.
- Run CI gates and secrets scanning directly from any supported AI client.
FAQ from Veto
Do I need an API key to use Veto?
On a subscription no extra token cost and no API key is needed. On pay-per-token billing, Veto detects API keys and warns you about optional LLM call usage.
Does Veto always make LLM calls?
No. Agents run as real expert modules (OWASP/CWE rules, AST secret detection, complexity metrics) at zero token cost. They optionally upgrade to LLM reasoning only when your client supports it.
What does "cross-CLI memory" mean?
You can save a session in one tool (e.g., Claude Code) and resume it in another supported tool (e.g., Cursor) with full context intact.
Is Veto open source?
Yes, Veto is MIT licensed and available on npm and the official MCP registry (io.github.jigyasudham/veto).
How are guardrails implemented?
Veto includes dependency-hallucination detection, decision-drift enforcement, and a compounding-error circuit breaker that catches mistakes the AI itself makes.
More Developer Tools MCP servers
TalkToFigma
sonnylazuardiTalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.
Smithery CLI
smithery-aiInstall, manage and develop MCP servers and skills for agents
nuxt-mcp / vite-plugin-mcp
antfuMCP server helping models to understand your Vite/Nuxt app better.
sentry-mcp
getsentryAn MCP server for interacting with Sentry via LLMs.
DevDocs by CyberAGI 🚀
cyberagiincCompletely free, private, UI based Tech Documentation MCP server. Designed for coders and software developers in mind. Easily integrate into Cursor, Windsurf, Cline, Roo Code, Claude Desktop App
Comments