2ools vs Convika — MCP Server Comparison | AllMCPs
2ools vs Convika
A side-by-side look at the 2ools and Convika MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose 2ools for gaming work over a hosted endpoint; choose Convika for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 2ools when
You need dedicated capabilities in the Gaming domain.
You prefer a remote HTTP/SSE transport.
You want tools like create_public_preview, build_from_conversation, refine_project.
No tool names declared yet. Check the project README from the .
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.
2ools is categorized under Gaming and uses a remote HTTP/SSE transport. Convika belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick 2ools for gaming work and Convika for developer tools.
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.
2ools has no declared pricing — check the project's own site. Convika 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 2ools-2 and convika-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, 2ools has a quality signal of 51/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Convika has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.