A side-by-side look at the Wynncraft and Unity MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Wynncraft for gaming work as a local process; choose Unity MCP for gaming as a local process. You can also run both side by side in one mcpServers block.
combatGlobalLevel, professionsGlobalLevel, guildLevel.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 52/100 · Good | 56/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 | 0 | 4,508 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 1 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Wynncraft | View Unity MCP |
combatGlobalLevelprofessionsGlobalLevelguildLevelglobalPlayerContentNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"wynncraft": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-wynncraft"
]
}
}
}
{
"mcpServers": {
"ivanmurzak-unity-mcp": {
"command": "npx",
"args": [
"-y",
"unity-mcp-cli"
]
}
}
}