Wallpaper Engine MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| timeoutMs | No | 单次操作等待上限，1000–30000 毫秒 (per-operation timeout, 1000-30000 milliseconds) | |
| workspace | No | 受管工程、检查点、预览副本、截图和发布暂存目录 (managed projects, checkpoints, preview copies, screenshots and publish staging directory) | .we-mcp |
| installDir | No | 官方引擎安装目录，包含 wallpaper32.exe 或 wallpaper64.exe (Wallpaper Engine installation directory containing wallpaper32.exe or wallpaper64.exe) | |
| devtoolsPort | No | 手动配置的本机 CEF 调试端口；null 时只提供 CLI 和工程能力 (manually configured local CEF debugging port; when null, only CLI and project capabilities are available) | |
| projectRoots | No | 额外只读工程目录；可以是工程本身或其父目录；不扫描整盘 (additional read-only project directories; may be the project itself or its parent directory) |
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 |
|---|---|
| we_environment_probeA | Read configured engine version and actual capability evidence. Does not change engine settings. |
| we_project_listB | Discover projects only beneath configured roots; external sources are read-only. |
| we_project_inspectB | Return content revision, manifest, bounded file inventory and optionally up to 256 KiB of requested source text. |
| we_project_createB | Create offline Web starfield, or copy an existing source into the managed workspace. New copies strip workshopid. Scene copies remain unverified. |
| we_project_applyA | Apply project-relative UTF-8 writes/deletions using expectedRevision. Validates candidate and saves a persistent checkpoint before writing. |
| we_project_restoreA | Restore a checkpoint belonging to this managed project, refusing concurrent changes. Creates another checkpoint for undo. |
| we_project_validateA | Check metadata and static HTML/CSS references. Reports remaining runtime/editor checks without claiming engine validation. |
| we_preview_openC | Launch a uniquely named official engine window from an immutable source snapshot. Reports evidence or explicit unverified state; never changes the desktop wallpaper. |
| we_preview_set_propertiesA | Validate and send named properties only to an owned preview window; source defaults stay unchanged. |
| we_preview_observeB | Read owned CEF target diagnostics, bounded console/network events and PNG frames. reload reloads the fixed preview snapshot; open a new preview for newer source revisions. |
| we_preview_closeA | Close only a window created by this server session. No global stop/kill commands. |
| we_publish_prepareB | Stage offline runtime sources and a preparation report; never packs native assets or uploads to Workshop. |
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 12 tools
Tools split cleanly into project, preview, and environment concerns, with actions like inspect, validate, apply, and restore each having a distinct stated scope. Descriptions explicitly clarify what each tool does and does not do, so selection should be unambiguous.
All names use snake_case with a consistent we_ prefix and object_action structure, such as we_project_apply and we_preview_open. There are no mixed conventions or vague verbs.
12 tools is well-scoped for the domain, covering project lifecycle, preview control, and environment inspection without obvious redundancy or missing basic operations.
Core project and preview lifecycle is covered, including create, edit, restore, validate, and preview observation. However, there is no final publish/upload tool and no project deletion or checkpoint listing, leaving some end-to-end workflows incomplete or requiring external steps.