Ext Ops Panel
Open dashboard
Comparison

Gameye vs io.github.YawLabs/mcph

Gameye is an MCP server published by Gameye. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.YawLabs/mcph is an MCP server published by YawLabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceGameyeio.github.YawLabs/mcph
Official MCP Registry Listed
Version: 0.4.0
Downloads/month (npm): 901
Downloads/week (npm): 113
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed, marked deprecated
Version: 0.57.1
Downloads/month (npm): 228
Downloads/week (npm): 20
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Gameye vs io.github.YawLabs/mcph
FactGameyeio.github.YawLabs/mcph
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-25Not published
Where it runs (differs)On your machine (gameye-mcp)On your machine (@yawlabs/mcph)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/gameye/gameye-mcpNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Gameye

In its own words, on Official MCP Registry:

Launch, inspect and stop multiplayer game server sessions on Gameye from any MCP client.

io.github.YawLabs/mcph

In its own words, on Official MCP Registry:

mcp.hosting — one install, all your MCP servers, managed from the cloud

How to run each

Gameye As a local MCP server: npm package

Claude Code
claude mcp add --env "GAMEYE_API_TOKEN=<YOUR_GAMEYE_API_TOKEN>" --transport stdio gameye-mcp -- npx -y gameye-mcp

Requires: GAMEYE_API_TOKEN (secret)

io.github.YawLabs/mcph As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcph -- npx -y @yawlabs/mcph

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.YawLabs/mcph publish no settings it asks for, so we do not compare settings.

What it can do: Gameye · What it can do: io.github.YawLabs/mcph · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built