Gaming Feeds vs Vivarium
A side-by-side look at the Gaming Feeds 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 Gaming Feeds 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 Gaming Feeds when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_feeds, read_feed, fetch_feed.
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 | 48/100 · Fair | 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 | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Gaming Feeds | View Vivarium |
Tools & capabilities
Gaming Feeds tools 3
list_feedsList the curated gaming feeds (id, title, category, source). Optionally filter by category (gaming) or keyword. Pass an id to read_feed.read_feedRead a curated gaming feed by its id (from list_feeds). Returns normalized items (title, link, published, summary). Optionally filter items by keyword.fetch_feedFetch and normalize any RSS / Atom / RDF feed by URL. CF-robust: fetches directly and falls back to a proxy if the source blocks the gateway. Use list_feeds first for curated sources.
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.
Gaming Feeds
{
"mcpServers": {
"gaming-feeds": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-gaming-feeds"
]
}
}
}
Vivarium
{
"mcpServers": {
"vivarium": {
"command": "npx",
"args": [
"-y",
"vivarium-mcp"
]
}
}
}
Frequently asked questions
Gaming Feeds is categorized under Gaming and uses a local stdio subprocess. Vivarium belongs to Gaming and uses a local stdio subprocess. Pick Gaming Feeds 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.
Gaming Feeds 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 gaming-feeds and vivarium as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gaming Feeds has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Vivarium has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.