wallpaper-engine
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@wallpaper-engineShow Wallpaper Engine projects I can use as a Codex skin."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Wallpaper Engine Skin for Codex
English | 简体中文
A Codex plugin that uses compatible media from installed Wallpaper Engine projects as the background of the Codex app itself. It does not change the Windows desktop wallpaper and does not require DSH or Cordis.
Project lineage: this Codex edition is developed from the repository's original DSH Wallpaper Engine integration. The runtime has since been rewritten specifically for Codex; the former DSH/Cordis artifacts are retained in Git history, not in the current distribution. See NOTICE.md.
How it works
The plugin discovers local Steam/Wallpaper Engine projects, safely embeds compatible media, and inserts it behind the Codex UI through a local Chrome DevTools connection. The bundled launcher starts the official installed Codex executable with debugging bound to 127.0.0.1; no Codex files are patched or replaced.
Small video files render as looping video when they fit the safe inline-media limit.
Videos over 48 MB are automatically cached as full-duration MP4 files capped at 2560×1440, 30 FPS, and about 10 Mbps. Cached results are reused; outputs still over 512 MB fall back to a decoded animation sequence. Web, Scene, or Application projects use their preview image.
CDP access is allowlisted to the exact Codex main-page URL
app://-/index.html; browser tabs, WebViews, login pages, HTTPS pages, and other debug targets are never inspected or modified.The injected “皮肤调整” panel can switch among local video projects and controls fit mode, zoom, position, panel opacity, scrim, and blur.
Video switching shows an indeterminate preparation bar during transcoding and measured 0–100% progress during transfer; success turns green and failure turns red.
Video and frame animation pause automatically while Codex is unfocused, minimized, or hidden, then resume when Codex becomes active.
Transcoded files are stored under
%LOCALAPPDATA%\CodexWallpaperEngineSkin\transcoded; source Wallpaper Engine projects are never modified.The selected skin and adjustment settings persist under
%LOCALAPPDATA%\CodexWallpaperEngineSkin. Ending a task no longer removes the layer, and a Codex instance started with the bundled launcher restores the last enabled skin automatically.codex_skin_removeremoves the layer and clears the saved preference.
Dynamic backgrounds are experimental: Codex's supported Appearance settings cover colors, fonts, contrast, and translucency, but do not currently provide a public background-media extension point. The plugin can also generate a native codex-theme-v1 color-theme string as a supported fallback.
Related MCP server: Codex Image Control MCP Server
Quick install and usage
This repository is the plugin root. It requires Node.js 22 or newer and only uses Node.js built-ins, so npm install is unnecessary.
Paste this line into PowerShell:
$p = Join-Path $env:TEMP 'install-codex-wallpaper-skin.ps1'; Invoke-WebRequest 'https://raw.githubusercontent.com/JonathandNidhog/dsh-plugin-wallpaper-engine-codex/main/install.ps1' -OutFile $p; powershell -NoProfile -ExecutionPolicy Bypass -File $pThe installer downloads or updates the repository, registers the personal Codex marketplace entry, installs the plugin, and creates a Codex Wallpaper Skin shortcut on the desktop and Start menu. Run the same command again later to update.
If regular Codex is already running, the shortcut asks whether to restart it with skin support. It no longer closes silently; choosing No leaves the current task untouched.
After installation:
Close every Codex window.
Launch
Codex Wallpaper Skinfrom the desktop or Start menu.In a new Codex task, ask to list compatible Wallpaper Engine skins and apply one.
The launcher refuses to continue while Codex is already running. A normal Codex launch has no debug endpoint and cannot accept a dynamic skin; this remains necessary because Codex does not expose a public background-image API. To use another loopback debug port, pass -Port to the launcher and set CODEX_SKIN_CDP_PORT to the same value for the plugin process.
Developers can also clone the repository, register it in a local Codex marketplace manually, and run scripts/launch-codex-with-skin.ps1 directly.
Example requests
“Show Wallpaper Engine projects I can use as a Codex skin.”
“Apply the Neon City background to Codex with more transparency.”
“Remove the Codex skin.”
“Generate a dark native Codex theme with a blue accent.”
If source discovery fails, set WALLPAPER_ENGINE_HOME to the Wallpaper Engine directory, or set WALLPAPER_ENGINE_STEAM_ROOT to the Steam root.
Development
npm run verifyThe MCP server communicates through JSON-RPC over stdio. Wallpaper Engine projects are read-only; arbitrary media paths are not accepted.
Repository layout
Path | Purpose |
| Codex plugin manifest |
| Local MCP server registration |
| One-command installer and updater for end users |
| Codex skill workflow and safety rules |
| MCP tool server |
| Codex launcher, video transcoding, and frame fallback |
| Wallpaper discovery and Codex skin bridge |
| Node test suite |
Legacy DSH bundles, Cordis patches, generated lib/ artifacts, and embedded type archives are intentionally excluded from the current Codex distribution.
License
MIT. See NOTICE.md for project lineage. Wallpaper Engine and installed project content belong to their respective owners.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseBqualityDmaintenanceConnects AI assistants to a local Codex engine for performing deep, project-level code reviews and automated refactoring. It enables context-aware bug fixes and multi-file analysis through a standardized bridge between modern AI clients and local development environments.42
- AlicenseNot gradedqualityAmaintenanceEnables local image generation control and storyboard planning within Codex, supporting continuous image editing, formal image writing, video prompt management, and user-configured video connectors.Apache 2.0
- AlicenseAqualityBmaintenanceA project-local MCP bridge that allows Codex Desktop to plan tasks and OpenCode to execute them within the current project directory, with session reuse and native OpenCode background subagents.41MIT
- AlicenseNot gradedqualityBmaintenanceEnables local-first knowledge management for Codex, providing tools for guided discussions, contextual recall, review, and daily topics.MIT
Related MCP Connectors
Persistent memory layer that saves and recalls your project context and preferences.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/JonathandNidhog/dsh-plugin-wallpaper-engine-codex'
If you have feedback or need assistance with the MCP directory API, please join our Discord server