A side-by-side look at the Unity MCP and Wisp MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
Wisp MCP 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.
No confirmed install command for Wisp MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Unity MCP is categorized under Gaming and uses a local stdio subprocess. Wisp MCP belongs to Gaming and uses an install path we have not confirmed yet. Pick Unity MCP for gaming work and Wisp 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. Wisp MCP has no confirmed install command yet — follow its own setup instructions.
Unity MCP is listed as free. Auth: oauth 2.0. Wisp 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 ivanmurzak-unity-mcp and wisp-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Unity MCP has a quality signal of 56/100 (Good) with 4 views, 0 installs and 4,418 GitHub stars. Wisp MCP has 31/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.