world-of-claudecraft-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WOC_ENV_SERVER | Yes | Path to the env_server.cjs executable |
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 |
|---|---|
| wow_infoA | Return environment metadata: observation size, number of actions, the full action vocabulary, and max level. Call once at the start to learn the action names. |
| wow_list_actionsA | List the available action names for the current class setup. Same as wow_info action list. |
| wow_resetA | Start a NEW episode (or restart after one ends). Returns the initial decoded game state. player_class examples: warrior, paladin, priest, mage, hunter, rogue, warlock, druid, shaman. |
| wow_stepA | Take ONE named action and advance the sim by one env step (5 sim ticks ~ 0.25s). Returns reward, end flags, and the new decoded state. |
| wow_playA | Apply a SEQUENCE of named actions, one env step each. Fewer round-trips than calling wow_step repeatedly, so prefer batches of 1-10 actions per call. Stops early if the episode ends. Returns total reward, end flags, and final state. |
| wow_stateA | Re-decode and return the CURRENT game state without taking any action. Use this to read the situation before deciding. |
| wow_closeA | Shut down the environment subprocess. Call when you are completely done playing. |
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 7 tools
Most tools have distinct purposes, but wow_info and wow_list_actions overlap in listing actions, causing minor ambiguity. The distinction between wow_step and wow_play is clear (single vs batch).
All tools start with 'wow_' and use underscores, but some verbs are nouns (wow_state) and two tools (info, list_actions) serve similar informational roles with different names.
7 tools is well-scoped for a game environment MCP server, covering reset, step, batch play, shutdown, info, actions, and state without unnecessary extras.
The tool surface covers all essential operations for interacting with a game environment: starting, stepping, batching, closing, metadata, and state reading. No obvious gaps.