Game ops — player & rewards-economy MCPs
When to use this skill
- Player lookups: account, wallet, ban/unban, leaderboard state (Nakama).
- Feature flags and live configs on the game backend.
- Rewards economy: brands, quests, offers, redemptions, gift cards,
staking, coupons, fraud checks (QuestX).
The tiles in this group
Registry group game-ops. Gateway tileId is what admin_call_mcp takes.
| Tile id |
Gateway tileId |
What it does |
Auth |
nakama-console |
nakama |
Game-ops MCP: player inspect, wallets, flags, configs, generic RPC |
Server-side admin auth (http_key) baked; no token needed. Endpoint https://nakama-mcp.intelli-verse-x.ai/. |
quests |
questx |
QuestX rewards economy, ~120 tools: brands, quests, offers, redemptions, gift cards, staking, coupons, fraud checks |
No token needed. In-cluster only (quests-api.quests-economy.svc.cluster.local:3002/mcp, session handshake) — gateway required. |
Apps covered: intelliverse, quizverse, questx (per the tile appIds).
Portal-only tiles (no MCP — launch the UI): nakama-analytics
(retention/DAU/MAU dashboard), quizverse (quiz builder), quizx /
quizx-admin (storefront), game-dev-portal (developer onboarding).
How to reach them
Nakama direct attach: https://nakama-mcp.intelli-verse-x.ai/ — no
token needed (admin auth is server-side).
QuestX is in-cluster only — the gateway is the only path from outside:
admin_call_mcp { tileId: "questx", method: "tools/list" }
admin_call_mcp { tileId: "nakama", method: "tools/call",
tool: "<name from tools/list>", arguments: { ... } }
Neither registry entry enumerates every tool (QuestX has ~120) — start
with tools/list and filter by keyword (brand, quest, redemption, fraud,
gift, coupon, wallet, player) rather than reading the whole list.
Task recipes
Player investigation. Nakama: look up the player by username/id →
inspect account + wallet → check recent leaderboard entries. If the user
then asks for a ban, that's a write — confirm the exact account id first.
Redemption review. QuestX: list pending redemptions → pull the
conversion + fraud-check detail for the flagged ones → summarize evidence
per case; the approve/reject click stays with the operator
(/admin/gift-card-review in the portal).
"Which quests are live?" QuestX quest-listing tools → cross-reference
offers and brands → table of live quests with reward config.
Feature-flag check before a live-ops change. Nakama: read current
flags/configs → show the diff the user wants → apply only after approval
(flags change live game behavior for all players).
Cautions
- Bans, wallet adjustments, flag/config changes, and quest/offer mutations
all hit live players and real money value — always show what will
change and get approval.
- Nakama's generic RPC tool can call any of the 1000+ server RPCs — prefer
the purpose-built tools; use generic RPC only when you know the exact
RPC id and payload.
- Never paste keys into chat; Nakama and QuestX auth is baked server-side.
1---2name: ivx-mcp-game-ops3description: The "Game ops" MCP tiles — Nakama game backend (players, wallets, flags, configs) and the QuestX rewards economy (~120 tools for brands, quests, offers, redemptions, gift cards, fraud). Use for player lookups, bans, wallet inspection, and rewards-economy operations.4---56# Game ops — player & rewards-economy MCPs78## When to use this skill910- Player lookups: account, wallet, ban/unban, leaderboard state (Nakama).11- Feature flags and live configs on the game backend.12- Rewards economy: brands, quests, offers, redemptions, gift cards,13 staking, coupons, fraud checks (QuestX).1415## The tiles in this group1617Registry group `game-ops`. Gateway tileId is what `admin_call_mcp` takes.1819| Tile id | Gateway tileId | What it does | Auth |20|---|---|---|---|21| `nakama-console` | `nakama` | Game-ops MCP: player inspect, wallets, flags, configs, generic RPC | Server-side admin auth (`http_key`) baked; no token needed. Endpoint `https://nakama-mcp.intelli-verse-x.ai/`. |22| `quests` | `questx` | QuestX rewards economy, ~120 tools: brands, quests, offers, redemptions, gift cards, staking, coupons, fraud checks | No token needed. In-cluster only (`quests-api.quests-economy.svc.cluster.local:3002/mcp`, session handshake) — gateway required. |2324Apps covered: `intelliverse`, `quizverse`, `questx` (per the tile appIds).2526Portal-only tiles (no MCP — launch the UI): `nakama-analytics`27(retention/DAU/MAU dashboard), `quizverse` (quiz builder), `quizx` /28`quizx-admin` (storefront), `game-dev-portal` (developer onboarding).2930## How to reach them3132**Nakama direct attach:** `https://nakama-mcp.intelli-verse-x.ai/` — no33token needed (admin auth is server-side).3435**QuestX is in-cluster only — the gateway is the only path from outside:**3637```38admin_call_mcp { tileId: "questx", method: "tools/list" }39admin_call_mcp { tileId: "nakama", method: "tools/call",40 tool: "<name from tools/list>", arguments: { ... } }41```4243Neither registry entry enumerates every tool (QuestX has ~120) — start44with `tools/list` and filter by keyword (brand, quest, redemption, fraud,45gift, coupon, wallet, player) rather than reading the whole list.4647## Task recipes4849**Player investigation.** Nakama: look up the player by username/id →50inspect account + wallet → check recent leaderboard entries. If the user51then asks for a ban, that's a write — confirm the exact account id first.5253**Redemption review.** QuestX: list pending redemptions → pull the54conversion + fraud-check detail for the flagged ones → summarize evidence55per case; the approve/reject click stays with the operator56(`/admin/gift-card-review` in the portal).5758**"Which quests are live?"** QuestX quest-listing tools → cross-reference59offers and brands → table of live quests with reward config.6061**Feature-flag check before a live-ops change.** Nakama: read current62flags/configs → show the diff the user wants → apply only after approval63(flags change live game behavior for all players).6465## Cautions6667- Bans, wallet adjustments, flag/config changes, and quest/offer mutations68 all hit **live players and real money value** — always show what will69 change and get approval.70- Nakama's generic RPC tool can call any of the 1000+ server RPCs — prefer71 the purpose-built tools; use generic RPC only when you know the exact72 RPC id and payload.73- Never paste keys into chat; Nakama and QuestX auth is baked server-side.
intelli-verse-x