A side-by-side look at the Unity MCP and L2Tools — Lineage 2 Reference Data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Unity MCP for gaming work as a local process; choose L2Tools — Lineage 2 Reference Data for gaming. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | L L2Tools — Lineage 2 Reference Data | |
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 56/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,418 | — |
| Directory activity | 4 views 0 installs 1 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Unity MCP | View L2Tools — Lineage 2 Reference Data |
No tool names declared yet. Check the project README from the listing page.
No 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": {
"ivanmurzak-unity-mcp": {
"command": "npx",
"args": [
"-y",
"unity-mcp-cli"
]
}
}
}
No confirmed install command for L2Tools — Lineage 2 Reference Data yet — follow the setup steps linked from its listing page rather than a guessed package name.