nakama-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAKAMA_HOST | No | Host for both APIs. | 127.0.0.1 |
| NAKAMA_PORT | No | Client API port. | 7350 |
| NAKAMA_USE_SSL | No | Use https instead of http. | false |
| NAKAMA_SERVER_KEY | No | Server key for client authenticate endpoints. | defaultkey |
| NAKAMA_TIMEOUT_MS | No | Per-request timeout. | 15000 |
| NAKAMA_CONSOLE_PORT | No | Console API port. | 7351 |
| NAKAMA_CONSOLE_PASSWORD | No | Console admin password. | password |
| NAKAMA_CONSOLE_USERNAME | No | Console admin user. | admin |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nakama_search_actionsA | Search the Nakama API catalog (179 operations: 87 client, 92 console) by natural-language intent and get matching action IDs, HTTP method/path, summaries, and parameter schemas. Use this to discover the action_id you then pass to nakama_execute_action. Results include resolved request-body field schemas when available. Examples: 'list players', 'write storage object', 'leaderboard records', 'ban account', 'active matches'. |
| nakama_execute_actionA | Execute any Nakama operation by its action_id (from nakama_search_actions). Provide path_params, query_params, and/or body as needed. Auth is handled automatically: console actions auto-login with configured admin credentials; client actions use the player session from nakama_authenticate; authenticate endpoints use the server key. For calling server RPCs prefer nakama_call_rpc (it encodes the payload correctly). |
| nakama_authenticateA | Establish a player session for the client API (:7350). Required before calling other client/player endpoints. Supports device, custom, or email auth. The session token is held in memory for subsequent calls. |
| nakama_call_rpcA | Invoke a registered runtime RPC function by id over the client API. Pass payload as a JSON object or string; it is encoded as the gateway expects. Provide http_key to call an RPC without a player session; otherwise authenticate first with nakama_authenticate. |
| nakama_console_list_accountsA | List/search player accounts via the console API. Optional filter by user ID or username. |
| nakama_console_get_accountA | Fetch a single player account (profile, wallet, devices, linked logins) by user ID via the console API. |
| nakama_console_list_storageA | List storage objects via the console API, optionally filtered by collection, key, and/or owner user ID. |
| nakama_console_get_statusA | Return Nakama node status and lightweight service metrics (CPU, memory, latency, presences) via the console API. |
| nakama_write_storage_objectA | Write or update a single storage object as the authenticated player (call nakama_authenticate first). Pass value as an object or JSON string. Use version '*' to require the object not already exist. |
| nakama_write_leaderboard_recordA | Submit a score to a leaderboard as the authenticated player (call nakama_authenticate first). |
| nakama_send_notificationB | Send an in-app notification to a player via the console API. Use a positive app-defined code (<=0 is reserved). |
| nakama_ban_accountB | Ban a player account by user ID via the console API. |
| nakama_unban_accountA | Remove a ban from a player account by user ID via the console API. |
| nakama_healthcheckA | Probe both APIs: the client /healthcheck endpoint and a console status call (which also verifies admin login). Returns a per-surface reachability report. Use this first when calls are failing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have clear purposes, with console and client operations separated by naming. However, nakama_call_rpc and nakama_execute_action overlap in functionality, potentially causing confusion about which to use for RPC calls.
All tool names follow a consistent verb_noun pattern in snake_case, with console operations consistently prefixed by 'console_' and client operations by no prefix. This makes the set predictable and easy to navigate.
With 14 tools, the count is well-scoped for a game backend server covering authentication, account management, storage, leaderboards, notifications, RPCs, and healthcheck. This is within the ideal 3–15 range.
The tool set covers common tasks directly and provides a generic search-execute mechanism that can invoke all 179 Nakama API operations, ensuring no dead ends. Minor omissions like storage delete are handled via execute_action.