Veto vs Stackguide MCP
A side-by-side look at the Veto and Stackguide MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Veto for coding agents work as a local process; choose Stackguide MCP 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 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.
Choose Stackguide MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You want tools like
setup, context, rules.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 59/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 2 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 16 |
| Full listing | View Veto | View Stackguide MCP |
Tools & capabilities
Veto tools
No tool names declared yet. Check the project README from the listing page.
Stackguide MCP tools 16
setupconfigure StackGuide context for project typecontextshow currently loaded contextruleslist/search/get/select rule setsknowledgelist/search/get knowledge filesreviewanalyze files/URLs/project code qualitycursorbrowse/import community rulesdocsfetch/search/list documentationconfigsave/load/export/import configurationscustom_rulecreate/update/delete/list project custom ruleshelpusage help by topicgenerateboilerplate generation (component/hook/service/test/api/model/util)healthproject health score and recommendations- +4 more on 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.
Veto
{
"mcpServers": {
"jigyasudham-veto": {
"command": "npx",
"args": [
"-y",
"@jigyasudham/veto@latest"
]
}
}
}
Stackguide MCP
{
"mcpServers": {
"stackguide-mcp-2": {
"command": "npx",
"args": [
"-y",
"@stackguide/mcp-server@latest"
]
}
}
}
Frequently asked questions
Veto is categorized under Coding Agents and uses a local stdio subprocess. Stackguide MCP belongs to Coding Agents and uses a local stdio subprocess. Pick Veto for coding agents work and Stackguide MCP 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.
Veto is listed as free. Auth: no auth required. Stackguide MCP has no declared pricing — check the project's own site. 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 jigyasudham-veto and stackguide-mcp-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Veto has a quality signal of 59/100 (Good) with 3 views, 0 installs and 4 GitHub stars. Stackguide MCP has 53/100 (Good) with 0 views, 0 installs and 2 GitHub stars.