get_media_sessionsLABSCO SUMMARY
Desktop control with the window list attached, which is what makes it usable.
Focusing or closing a window means knowing which windows exist, and get_window_list plus get_foreground_window_info supply that before anything acts. Per-window screenshots are the other quietly useful piece — capturing one application instead of the whole desktop keeps whatever else is on screen out of the conversation. Everything runs with your own user permissions, so scope it accordingly.
What it is
A server over the Windows API. It covers the desktop operations that normally need a keyboard shortcut or a trip to Settings, exposed as individual tools.
What you get
- Media: get_media_sessions, play, pause, next and previous control whatever is currently playing
- Windows: get_foreground_window_info, get_window_list, focus_window, close_window and minimize_window
- screenshot_window captures a specific window rather than the whole screen
- Notifications: send_toast raises a Windows toast
- Monitors: sleep_monitors and wake_monitors
- Theme: get_theme_mode reads the current mode and set_theme_mode switches between light and dark
- Start menu: open_file and open_url launch through the shell
- Clipboard: get_clipboard and set_clipboard read and write it
Requirements
Windows, and the Python package mcp-windows, version 0.1.0 — run as uvx mcp-windows, or from a checkout with uv. No account and no key; the tools act with the permissions of the user running the server.
Setup effort
One command — uvx mcp-windows
USE CASES
01
Controlling playback without leaving what you are doing
Media sessions are enumerated first, then play, pause or skip.
02
Tidying the desktop
List the windows, then focus, minimise or close the ones you name.
03
Showing the assistant one application
Capture that window rather than the whole screen.
04
Moving text between the assistant and the desktop
Read and write the clipboard directly.
05
Getting told when something finishes
A Windows toast notification rather than a message you have to go and read.
20 tools
Listed in project docs. Your client may show a different list.
pauseplaynextprevioussend_toastget_foreground_window_infoget_window_listfocus_windowclose_windowminimize_windowscreenshot_windowsleep_monitorswake_monitorsset_theme_modeget_theme_modeopen_fileopen_urlget_clipboardset_clipboardBEFORE YOU INSTALL
What to know first
Tools you get
20 tools named in the project's documentation. pause, play, next and previous are media-control tools with single-word names; without them get_media_sessions can only report what is playing.
Requires
uvx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-windowsMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"windows": {
"command": "uvx",
"args": [
"mcp-windows"
]
}
}
}
