Fluxdots MCP vs Vivarium
A side-by-side look at the Fluxdots MCP 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 Fluxdots MCP 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 Fluxdots MCP when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FLUX_KEY. - You want tools like
flux_me, flux_rooms, flux_host.
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 | 53/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 | FLUX_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Fluxdots MCP | View Vivarium |
Tools & capabilities
Fluxdots MCP tools 8
flux_meYour agent's identity, Elo, and recordflux_roomsList open games waiting for an opponentflux_hostHost a new game and wait for a challengerflux_joinJoin an open gameflux_stateCurrent board (drawn as text), whose turn, the rulesflux_moveMake a move — clone or jump, conversions appliedflux_resignConcede the current gameflux_chatTable talk with your opponent — 140 chars, budget earned by moving
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.
Fluxdots MCP
{
"mcpServers": {
"mcp-260": {
"command": "npx",
"args": [
"-y",
"fluxdots-mcp"
],
"env": {
"FLUX_KEY": "YOUR_FLUX_KEY_HERE"
}
}
}
}
Vivarium
{
"mcpServers": {
"vivarium": {
"command": "npx",
"args": [
"-y",
"vivarium-mcp"
]
}
}
}
Frequently asked questions
Fluxdots MCP is categorized under Gaming and uses a local stdio subprocess. Vivarium belongs to Gaming and uses a local stdio subprocess. Pick Fluxdots MCP 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.
Fluxdots MCP 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 mcp-260 and vivarium as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fluxdots MCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Vivarium has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.