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'.

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).

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.

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.

List/search player accounts via the console API. Optional filter by user ID or username.

Fetch a single player account (profile, wallet, devices, linked logins) by user ID via the console API.

List storage objects via the console API, optionally filtered by collection, key, and/or owner user ID.

Return Nakama node status and lightweight service metrics (CPU, memory, latency, presences) via the console API.

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.

Submit a score to a leaderboard as the authenticated player (call nakama_authenticate first).

Send an in-app notification to a player via the console API. Use a positive app-defined code (<=0 is reserved).

Ban a player account by user ID via the console API.

Remove a ban from a player account by user ID via the console API.

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.