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.
V
Veto MCP Server
@jigyasudham
Basic information
About Veto MCP Server
93 agentic MCP tools + 49 specialist agents for every major AI CLI. Self-learning, no API keys.
Veto MCP Server config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"veto": {
"command": "npx",
"args": [
"-y",
"--package",
"@jigyasudham/veto",
"veto-server"
]
}
}
}Veto MCP Server tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
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.
Frequently asked questions
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
TaskerArmy Agent
TaskerArmyAsk Claude or ChatGPT what Shopify theme optimization tasks are pending on your store, a remote MCP server for TaskerArmy Agent accounts.
ArtiBot Cloud MCP - Zhijiangyun 智匠云
bofobArtiBot Cloud MCP (Zhijiangyun 智匠云) — cloud MCP server for robot manipulation data & GPU workloads. 15 tools: robot fleet management, data collection & video recording, post-processing pipelines, and benchmark evaluation
1
M
MeroFoundry
MERO Consulting IncMeroFoundry is a remote MCP server available at https://platform.merofoundry.com/mcp.
OrangePro
Aamir SiddiquiOrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.
12
Moxie Docs
Jackalope-DevAutomated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.
1
Comments