Valorant vs Wisp MCP
A side-by-side look at the Valorant and Wisp MCP 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 Wisp MCP for gaming. 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 Wisp MCP when
- You need dedicated capabilities in the Gaming domain.
- You have the keys it needs:
WISP_PANEL_URL, WISP_API_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 52/100 · Good | 31/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | WISP_PANEL_URLWISP_API_TOKEN |
| 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 Wisp MCP |
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.
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.
Valorant
{
"mcpServers": {
"valorant": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-valorant"
]
}
}
}
Wisp MCP
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
Valorant 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 Valorant 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.
Valorant has no declared pricing — check the project's own site. 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 valorant and wisp-mcp 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. Wisp MCP has 31/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.
