Inspeziere und verwalte Windows-Desktop-Umgebungen, einschließlich Monitoren, Fenstern, Audio und Systemeinstellungen, über einen agentengesteuerten Automatisierungs-Server.
Auch bekannt als EvotecIT/DesktopManager, desktopmanager
- Stars
- 108
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.2.3
- Letzter Commit
- 13. Nov. 2026
- Lizenz
- MIT
Was ist DesktopManager MCP?
Inspeziere und verwalte Windows-Desktop-Umgebungen, einschließlich Monitoren, Fenstern, Audio und Systemeinstellungen, über einen agentengesteuerten Automatisierungs-Server.
Zusammenfassung generiert aus dem README des Projekts
Über DesktopManager MCP server
DesktopManager Windows Verification bietet eine agentengesteuerte Automatisierungsumgebung, die für die Inspektion und Verwaltung von Windows-Desktop-Einstellungen entwickelt wurde. Er arbeitet als MCP server über den Befehl desktopmanager mcp serve und ermöglicht es KI-Agenten, über eine Standard-Input/Output-Schnittstelle mit dem lokalen Betriebssystem zu interagieren. Der Server folgt einem Inspect-First-Sicherheitsmodell, das es Agenten ermöglicht, den aktuellen Zustand einer Maschine zu beobachten, bevor sie Änderungen vornehmen versuchen.
Nutzer können eine Vielzahl von Systemkomponenten steuern, darunter Monitore, Fenster, Audio-Endpunkte und drahtlose Funkverbindungen. Das Toolkit verwaltet Display-Konfigurationen wie Auflösung, Ausrichtung und Hintergrundbilder und kümmert sich gleichzeitig um Fensterzustände, virtuelle Desktops und Workstation-Profile. Es bietet zudem Zugriff auf Funktionen auf Systemebene wie den Stromstatus, Sitzungsdiagnosen und Wi-Fi-Profilverbindungen. Da er mit nativen Windows-APIs interagiert, ist er speziell für Windows-Umgebungen konzipiert, um komplexe Desktop-Workflows zu automatisieren.
Was du damit machen kannst
- 1Workstation-Setups automatisierenEin Entwickler kann einen Agenten anweisen, ein gespeichertes Profil anzuwenden, das spezifische Monitor-Layouts und Audio-Einstellungen wiederherstellt.
- 2System- und Sitzungsstatus überwachenEin Agent kann den aktuellen Stromstatus prüfen oder untersuchen, welcher Benutzer in der aktiven Sitzung angemeldet ist.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
Automatisierte Checks
Geluften am 12. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertNicht geprüft
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
README
Auf GitHub ansehenDesktopManager - C# Library and PowerShell Module
DesktopManager is a Windows desktop automation toolkit available as a .NET library, PowerShell module, CLI, MCP server, and tray app.
The .NET library also exposes PortableDesktopService for current-user wallpaper, display discovery,
and session diagnostics on Windows, macOS, GNOME, and KDE Plasma. Each adapter reports its capabilities;
the window automation, tray app, CLI, and existing PowerShell commands retain their Windows scope.
See Portable desktop integration for usage and platform limits.
The .NET 8 and .NET 10 library targets support trimming and Native AOT, including Core Audio, wallpaper and monitor enumeration, Explorer folder capture, virtual desktops and UI Automation. The .NET Framework and .NET Standard targets retain their legacy interop paths. See Native AOT qualification for the contributor smoke consumer.
Threaded services use bounded kernel-event waits for startup and synchronous worker calls, including STA callers.
Startup normally has a five-second deadline; wallpaper/audio COM calls have a fifteen-second completion deadline,
and hotkey registration and clipboard writes have five seconds. UI Automation respects its invocation deadline.
A timeout cancels work that has not started. NativeOperationOutcomeUnknownException means a native operation
is already running and may still apply its change: inspect the target before retrying a mutation. An in-flight
native call cannot be terminated safely; its thread retains ownership and performs late-result cleanup.
You can also download it from PowerShell Gallery
If you would like to contact me you can do so via Twitter or LinkedIn.
What it's all about
DesktopManager provides one shared Windows automation core through five surfaces:
- C# library for .NET applications and services
- PowerShell module for scripts and operator workflows
- CLI executable for terminal and JSON automation
- MCP server for inspect-first agent automation
- Windows tray app for daily hotkeys and monitor actions
It has following features:
- Get information about monitors
- Get information about display devices
- Get information about wallpapers
- Set wallpapers
- Get/Set desktop background color
- Get/Set monitor position
- Get/Set window position
- Get/Set window state (minimize, maximize, restore)
- Capture desktop screenshots from all monitors, a single monitor or a custom region
- Manage monitor brightness
- Start/Stop/Advance wallpaper slideshows
- Track wallpaper history
- Adjust monitor resolution and orientation
- Move monitors around the virtual desktop
- Save and restore window layouts
- Snap or move windows between monitors
- Subscribe to resolution, orientation or display changes
- Keep inactive windows awake using periodic input
- Manage keep-alive sessions for windows
- Save and restore cohesive workstation profiles across displays, audio, personalization, and taskbars
- Enumerate Core Audio render/capture endpoints, change volume and mute, set default roles, and observe endpoint changes
- Inspect power and interactive-session state; lock, sign out, sleep, hibernate, or hold a bounded keep-awake lease
- Capture and restore personalization snapshots and configure taskbar visibility, position, and auto-hide
- Enumerate, observe, and explicitly enable or disable Wi-Fi, Bluetooth, mobile broadband, and FM radios through the supported Windows radio API
- List saved Windows Wi-Fi profiles and connect an exact saved profile without scanning nearby networks or exposing credentials
- Inspect a window's virtual desktop and move it to a known desktop through the public Windows virtual-desktop API
- Inspect and manage Plug and Play devices and Driver Store packages through documented native Windows APIs
Wallpaper consumers
Applications such as PowerBGInfo can read monitor geometry, display scale and the signed-in session user directly from the library:
using DesktopManager;
var monitors = new Monitors();
foreach (var display in monitors.GetMonitorSnapshots()) {
Console.WriteLine($"{display.Index}: {display.DeviceName}, " +
$"{display.Width} x {display.Height}, scale {display.Scale}");
}
var user = new DesktopSessionService().GetSessionUser();
Console.WriteLine(user?.AccountName ?? "Unknown");
Snapshots contain physical pixel bounds and per-monitor DPI even when the caller is not DPI aware. The calling thread's DPI context is restored. Indexes describe the current display topology; read them again after docking or reconnecting. Missing wallpaper device paths on session hosts are retained.
Monitors.SetLogonWallpaperWithResult(imagePath) sets the current account's lock screen through
Windows Runtime on .NET Framework, modern .NET and netstandard consumers. The result reports success,
the mechanism used and any failure. Machine policy fallback requires an explicit
allowPolicyFallback: true and elevation. The existing SetLogonWallpaper method keeps its automatic
policy fallback. See Wallpaper consumer APIs for examples, OS requirements,
policy limits and session deployment behavior.
Desktop state and controls
The workstation profile is the high-level entrypoint when you want to move between repeatable setups. It captures connected monitor modes and placement, monitor wallpaper and supported brightness/HDR state, active audio endpoint state and default roles, personalization, and taskbars. Applying a profile matches monitors by stable identity, stages display changes together, and rolls back the selected sections when a required step fails. Machine-wide personalization policies are captured but only restored when explicitly requested.
Save-DesktopWorkstationProfile -Name 'office'
Get-DesktopAudioEndpoint -DataFlow Render -ActiveOnly
Get-DesktopPowerStatus
Get-DesktopSession
Get-DesktopRadio
Get-DesktopWifiProfile
Connect-DesktopWifiProfile -Name 'Corporate WiFi'
Get-DesktopDevice -Present -Problem
Get-DesktopDriverPackage
Restore-DesktopWorkstationProfile -Name 'office' -Confirm
The same capabilities are available from the CLI:
desktopmanager workstation save --name office
desktopmanager audio list --flow render --active
desktopmanager system power
desktopmanager system session
desktopmanager radio list
desktopmanager wifi profiles
desktopmanager wifi connect --profile "Corporate WiFi"
desktopmanager device list --present --problem
desktopmanager driver list
desktopmanager workstation apply --name office
Radio control has two deliberately separate APIs. RadioService and the normal radio list / radio set commands use the supported Windows.Devices.Radios contract for individual radios. Global airplane mode uses an undocumented Windows shell COM contract, so it lives under ExperimentalAirplaneModeService and requires --experimental in the CLI, -Experimental in PowerShell, or --allow-experimental in MCP.
Wi-Fi profile connection is separate from radio control. WifiProfileService, Get-DesktopWifiProfile, and desktopmanager wifi profiles enumerate only profiles already stored by Windows. Connecting an exact profile uses the Native Wi-Fi profile API and ACM completion notifications; it does not scan nearby networks, return BSSIDs, expose profile XML or credentials, or query location-sensitive current-connection details. Windows still requires location consent for nearby-network scanning and related Wi-Fi information APIs. See Changes to API behavior for Wi-Fi access and location.
VirtualDesktopService exposes only the public Windows operations: check whether a top-level window is on the current desktop, get its desktop ID, and move it to a known desktop ID. Desktop enumeration, creation, renaming, switching, and removal are intentionally not presented as supported APIs.
Additional operator-focused docs for the newer CLI and MCP surfaces:
- Docs/DesktopManager.Cli.md
- Docs/DesktopManager.Mcp.md
- Docs/DesktopManager.Architecture.md
- Docs/DesktopManager.DesktopState.md
- Docs/DesktopManager.DeviceManagement.md
- Docs/DesktopManager.AutomationBasics.md
- Docs/DesktopManager.Plugin.md
- .agents/skills/desktopmanager-operator/SKILL.md
- .agents/skills/desktopmanager-build/SKILL.md
Which Surface Should You Use?
| Surface | Best for | Typical entrypoint |
|---|---|---|
| C# library | Embedding DesktopManager into your own .NET app or service | DesktopManager.dll |
| PowerShell module | Scripts, operators, admin workflows, repeatable task automation | Install-Module DesktopManager |
| CLI executable | Manual use, shell automation, JSON output, and MCP hosting | desktopmanager.exe |
| MCP server | Agent-driven automation over stdio with an inspect-first safety model | desktopmanager mcp serve |
| Windows tray app | Daily hotkeys, monitor bindings, HDR controls, tray runtime, and per-user startup | DesktopManager.App.exe |
How It Fits Together
DesktopManager now has one shared core and several operator-facing surfaces on top of it.
flowchart LR
A["Your .NET app"] --> B["DesktopManager library"]
C["PowerShell module"] --> B
D["desktopmanager.exe CLI"] --> B
E["MCP server"] --> D
J["DesktopManager.App tray app"] --> B
B --> F["Windows desktop APIs"]
F --> G["Monitors / wallpapers / brightness"]
F --> H["Windows / controls / input"]
F --> I["Layouts / snapshots / targets"]
If you want the fuller component and request-flow diagrams, see Docs/DesktopManager.Architecture.md.
The practical way to think about this:
- use the library when DesktopManager is part of your own application
- use PowerShell when you want scriptable admin/operator automation
- use the CLI when you want a human-friendly or JSON-friendly command surface
- use MCP when an agent should inspect first and mutate only through an explicit server session
Common Entry Points
| Goal | Recommended entrypoint |
|---|---|
| Add DesktopManager features to your own code | Reference the DesktopManager NuGet package |
| Run manual desktop operations from a terminal | desktopmanager.exe |
| Run DesktopManager every day from the tray | DesktopManager.App.exe or the DesktopManager MSI |
| Use it from PowerShell scripts | DesktopManager PowerShell module |
| Connect an agent/tooling layer | desktopmanager mcp serve |
| Understand the overall wiring | Docs/DesktopManager.Architecture.md |
Request Flow at a Glance
flowchart LR
A["User, script, or agent"] --> B{"Surface"}
B -->|".NET"| C["DesktopManager library"]
B -->|"PowerShell"| D["Cmdlets"]
B -->|"CLI"| E["desktopmanager.exe"]
B -->|"MCP"| F["desktopmanager mcp serve"]
B -->|"Tray app"| J["DesktopManager.App.exe"]
D --> C
E --> G["DesktopOperations"]
F --> G
J --> C
G --> C
C --> H["Win32, UI Automation, monitor, screenshot, and input services"]
The important part is that CLI, MCP, and PowerShell are meant to stay aligned by reusing the same shared C# behavior rather than inventing separate desktop logic in each surface.
Available PowerShell Cmdlets
| Cmdlet | Description |
|---|---|
| Get-DesktopMonitor | Retrieve monitor information with filtering options |
| Get-DesktopWallpaper | Get current wallpaper path for monitors |
| Set-DesktopWallpaper | Apply wallpaper from path, URL or stream |
| Get-DesktopWallpaperHistory | List stored wallpaper history entries |
| Set-DesktopWallpaperHistory | Update or clear wallpaper history file |
| Get-DesktopSlideshow | Inspect slideshow images, state, options and tick interval |
| Set-DesktopSlideshowOptions | Update slideshow shuffle behavior and tick interval |
| Start-DesktopSlideshow | Begin wallpaper slideshow across monitors |
| Stop-DesktopSlideshow | Stop currently running slideshow |
| Step-DesktopSlideshow | Move slideshow forward or backward |
| Get-DesktopBackgroundColor | Read current desktop background color |
| Set-DesktopBackgroundColor | Change desktop background color |
| Get-DesktopBrightness | Read monitor brightness level |
| Set-DesktopBrightness | Set monitor brightness level |
| Set-DesktopPosition | Move a monitor by its top-left coordinates without changing resolution |
| Set-DesktopResolution | Change monitor resolution or orientation |
| Set-DefaultAudioDevice | Set the default audio playback device |
| Get-DesktopAudioEndpoint | List Core Audio render and capture endpoints with volume, mute, and default roles |
| Set-DesktopAudioEndpoint | Set endpoint volume, mute, or selected default roles |
| Register-DesktopAudioEvent | Subscribe to endpoint, state, property, and default-role changes |
| Save-DesktopWorkstationProfile | Capture displays, audio, personalization, and taskbars as one named profile |
| Get-DesktopWorkstationProfile | List or load named workstation profiles |
| Restore-DesktopWorkstationProfile | Apply a named workstation profile with matching and rollback options |
| Remove-DesktopWorkstationProfile | Delete a named workstation profile |
| Get-DesktopPowerStatus | Read AC and battery state |
| Get-DesktopSession | Read current interactive-session identity, connection, lock, and idle state |
| Register-DesktopSessionEvent | Subscribe to meaningful session changes |
| Lock-DesktopSession | Lock the current Windows session |
| Exit-DesktopSession | Sign out the current Windows session with confirmation support |
| Start-DesktopKeepAwake | Hold a bounded system/display keep-awake lease |
| Suspend-DesktopSystem | Request sleep or hibernation with confirmation support |
| Get-DesktopPersonalization | Capture current state or list/load saved personalization snapshots |
| Save-DesktopPersonalization | Save a named personalization snapshot |
| Set-DesktopPersonalization | Apply explicit personalization settings |
| Restore-DesktopPersonalization | Restore a named personalization snapshot |
| Remove-DesktopPersonalization | Delete a named personalization snapshot |
| Get-DesktopTaskbar | List taskbars with monitor mapping, visibility, edge, and bounds |
| Set-DesktopTaskbarAutoHide | Set the explicit taskbar auto-hide state |
| Get-DesktopRadio | List radios through the supported Windows radio API |
| Set-DesktopRadio | Explicitly enable or disable matching supported radios |
| Register-DesktopRadioEvent | Subscribe to supported radio state changes |
| Get-DesktopWifiProfile | List saved Windows Wi-Fi profiles without scanning nearby networks |
| Connect-DesktopWifiProfile | Connect an exact saved Windows Wi-Fi profile |
| Get-DesktopAirplaneMode | Read the experimental global airplane-mode state after explicit acknowledgement |
| Set-DesktopAirplaneMode | Apply and verify experimental global airplane mode after explicit acknowledgement |
| Get-DesktopVirtualDesktop | Inspect the supported virtual-desktop state for a top-level window |
| Move-DesktopWindowToVirtualDesktop | Move a top-level window to a known virtual-desktop ID |
| Get-LogonWallpaper | Get the lock screen wallpaper path |
| Set-LogonWallpaper | Set the lock screen wallpaper |
| Set-TaskbarPosition | Move or hide the taskbar |
| Invoke-DesktopMouseMove | Move the mouse cursor |
| Invoke-DesktopMouseClick | Simulate a mouse click |
| Invoke-DesktopMouseScroll | Scroll the mouse wheel |
| Invoke-DesktopScreenshot | Capture monitor or region screenshots |
| Get-DesktopWindow | Enumerate visible windows |
| Get-DesktopWindowGeometry | Return outer-window and client-area geometry for matched windows |
| Get-DesktopWindowControl | Enumerate Win32 or UIA window controls |
| Get-DesktopWindowControlDiagnostic | Explain Win32 vs UIA control discovery and actionability |
| Get-DesktopWindowProcessInfo | Return process details for matched windows |
| Get-DesktopWindowTarget | List saved window-relative targets or resolve one against live windows |
| Get-DesktopControlTarget | List saved control targets or resolve one against live windows |
| Get-DesktopHostedSessionDiagnostic | Read the latest hosted-session typing diagnostic artifact or a specific one |
| Invoke-DesktopControlClick | Click a matched control using shared control action routing |
| Invoke-DesktopWindowClick | Click a window-relative point or saved window target |
| Invoke-DesktopWindowDrag | Drag between window-relative points or saved targets |
| Invoke-DesktopWindowScroll | Scroll at a window-relative point or saved target |
| Send-DesktopControlKey | Send keys to a matched control without reimplementing key routing |
| Set-DesktopControlTarget | Save a reusable control selector profile |
| Set-DesktopControlText | Write text directly to a specific control |
| Set-DesktopWindow | Move, resize or control windows |
| Set-DesktopWindowSnap | Snap window to common positions |
| Set-DesktopWindowTarget | Save a reusable window-relative point target |
| Set-DesktopWindowText | Paste or type text into a window |
| Wait-DesktopWindow | Wait for a window to appear |
| Wait-DesktopWindowControl | Wait for a control to appear |
| Test-DesktopWindow | Verify that a window exists or matches the active window |
| Test-DesktopWindowControl | Verify that a control exists |
| Start-DesktopWindowKeepAlive | Send periodic input to keep a window awake |
| Stop-DesktopWindowKeepAlive | Stop sending keep-alive input |
| Get-DesktopWindowKeepAlive | List windows with active keep-alive |
| Save-DesktopWindowLayout | Save current window layout to file |
| Restore-DesktopWindowLayout | Restore saved window layout |
| Register-DesktopMonitorEvent | Subscribe to display configuration changes |
| Register-DesktopOrientationEvent | Subscribe to orientation changes |
| Register-DesktopResolutionEvent | Subscribe to resolution changes |
DesktopManager MCP Fragen
Was kann der MCP server tun?
Der MCP server bietet agentengesteuerte Automatisierung unter Verwendung eines Inspect-First-Sicherheitsmodells, um Windows-Desktop-Elemente zu verwalten.
Unterstützt er das Fenster-Management?
Ja, er kann Fensterpositionen und Zustände wie Minimieren, Maximieren oder Wiederherstellen abrufen oder setzen.
Wie wird Audio gehandhabt?
Er kann Core Audio Render/Capture-Endpunkte aufzählen, die Lautstärke ändern, stummschalten und Standardrollen festlegen.