Valorant vs Vivarium
A side-by-side look at the Valorant and Vivarium MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Valorant for gaming work as a local process; choose Vivarium 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 Valorant when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_agents, get_agent, list_weapons.
Choose Vivarium when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 52/100 · Good | 39/100 · Fair |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Valorant | View Vivarium |
Tools & capabilities
Valorant tools 4
list_agentsVALORANT reference data (valorant-api.com) — list playable agents with their roles and abilities. Static game data, keyless. Optionally filter by role.get_agentVALORANT reference data (valorant-api.com) — full details for one agent by uuid: description, role, role description, and all abilities. Static game data, keyless.list_weaponsVALORANT reference data (valorant-api.com) — list weapons with category, cost, fire-rate, and magazine size. Static game data, keyless.list_mapsVALORANT reference data (valorant-api.com) — list maps with tactical description and icon. Static game data, keyless.
Vivarium 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.
Valorant
{
"mcpServers": {
"valorant": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-valorant"
]
}
}
}
Vivarium
{
"mcpServers": {
"vivarium": {
"command": "npx",
"args": [
"-y",
"vivarium-mcp"
]
}
}
}
Frequently asked questions
Valorant is categorized under Gaming and uses a local stdio subprocess. Vivarium belongs to Gaming and uses a local stdio subprocess. Pick Valorant for gaming work and Vivarium 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.
Valorant has no declared pricing — check the project's own site. Vivarium 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 valorant and vivarium as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Valorant has a quality signal of 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Vivarium has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.