Chess UCI vs Vibe MCP
A side-by-side look at the Chess UCI and Vibe MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chess UCI for gaming work as a local process; choose Vibe MCP for gaming as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Chess UCI when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
Choose Vibe MCP when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VIBE_API_URL, VIBE_EXTRAS. - You want tools like
vibe_start, vibe_init, vibe_who.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 39/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | VIBE_API_URLVIBE_EXTRAS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View Chess UCI | View Vibe MCP |
Tools & capabilities
Chess UCI tools
No tool names declared yet. Check the project README from the listing page.
Vibe MCP tools 9
vibe_startEntry point — authenticates, shows presence, checks inboxvibe_initSet up your identity (GitHub OAuth)vibe_whoSee who's online and what they're buildingvibe_dmSend a direct messagevibe_inboxCheck your unread messagesvibe_statusSet your mood (shipping, thinking, debugging, etc.)vibe_shipShare what you shippedvibe_discoverFind people building similar thingsvibe_helpShow available commands
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.
Chess UCI
{
"mcpServers": {
"chess-uci": {
"command": "uvx",
"args": [
"chess-uci-mcp@latest"
]
}
}
}
Vibe MCP
{
"mcpServers": {
"vibe-mcp": {
"command": "npx",
"args": [
"-y",
"slashvibe-mcp"
],
"env": {
"VIBE_API_URL": "YOUR_VIBE_API_URL_HERE",
"VIBE_EXTRAS": "YOUR_VIBE_EXTRAS_HERE"
}
}
}
}
Frequently asked questions
Chess UCI is categorized under Gaming and uses a local stdio subprocess. Vibe MCP belongs to Gaming and uses a local stdio subprocess. Pick Chess UCI for gaming work and Vibe MCP for gaming.
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.
Chess UCI has no declared pricing — check the project's own site. Vibe 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 chess-uci and vibe-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chess UCI has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Vibe MCP has 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars.