Amicus vs Veto
A side-by-side look at the Amicus and Veto MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Amicus for coding agents work as a local process; choose Veto for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Amicus when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Choose Veto when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 45/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Amicus | View Veto |
Tools & capabilities
Amicus tools
No tool names declared yet. Check the project README from the listing page.
Veto tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Amicus
{
"mcpServers": {
"amicus": {
"command": "npx",
"args": [
"-y",
"amicus@latest"
]
}
}
}
Veto
{
"mcpServers": {
"jigyasudham-veto": {
"command": "npx",
"args": [
"-y",
"@jigyasudham/veto@latest"
]
}
}
}
Frequently asked questions
Amicus is categorized under Coding Agents and uses a local stdio subprocess. Veto belongs to Coding Agents and uses a local stdio subprocess. Pick Amicus for coding agents work and Veto for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Amicus has no declared pricing — check the project's own site. Veto is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add amicus and jigyasudham-veto as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Amicus has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Veto has 59/100 (Good) with 3 views, 0 installs and 4 GitHub stars.