Hermes_WorldKit_MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORLDKIT_MCP_TOKEN | Yes | A random token used for authenticating the Godot editor bridge. | |
| WORLDKIT_MCP_WS_HOST | No | The hostname to bind the WebSocket endpoint. Only loopback values are accepted. | 127.0.0.1 |
| WORLDKIT_MCP_WS_PORT | No | The port for the WebSocket endpoint. Use 0 only in tests that supply the chosen URI to Godot. | 6506 |
| WORLDKIT_PROJECT_ROOT | Yes | The absolute path to the Godot project that the server controls. | |
| WORLDKIT_MCP_REQUEST_TIMEOUT | No | Timeout in seconds for bridge requests. | 5.0 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| worldkit_statusA | Report whether the pinned WorldKit Godot editor bridge is connected. |
| worldkit_capabilitiesA | List the safe WorldKit MCP tools and authenticated editor capabilities. |
| worldkit_scene_summaryA | Summarize bounded nodes in the scene currently open for editing in Godot. |
| worldkit_selected_nodesA | List bounded selected nodes owned by the current edited scene. |
| worldkit_select_nodeC | Select a canonical relative node path only if the inspected scene token matches. |
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 5 tools
Each tool addresses a distinct concern: connection status, capability discovery, scene content, current selection, and changing selection. The two node-related tools are separated by summary versus selected state, and the action verb in select_node makes its purpose clear.
All tools share a consistent worldkit_ prefix and snake_case style, which makes them predictable. However, most names are noun-like while select_node is the only verb-led name, so the pattern is not perfectly uniform.
Five tools is a tight, well-scoped set for a safe editor bridge. Each tool covers a necessary operation without redundancy.
The surface covers the core read-only workflow: verify connection, discover capabilities, summarize the scene, inspect selected nodes, and change selection. Minor gaps like deselecting or retrieving a specific node's full details are absent but are not fatal for the apparent safe-introspection purpose.