MCP Windows

You run an MCP server that enables a Windows API bridge, exposing media control, window management, screenshots, theme, start menu actions, and clipboard operations to MCP clients. This server lets you automate and orchestrate Windows features from your MCP workflow, making it practical to control apps, monitor state, and respond to events from a central client.

How to use

Connect to the Windows MCP server with your MCP client by selecting the Windows MCP server entry and establishing a connection. Once connected, you can issue commands to manage media playback, adjust system theme, interact with the foreground window, capture screenshots, and handle clipboard data. Use the client’s action panel or RPC bindings to call the available endpoints in real time.

Practical usage patterns you can perform include: starting or stopping media playback, sending on‑screen notifications, querying the current foreground window, listing all windows, focusing or closing a window, taking a screenshot of a specific window, putting monitors to sleep or waking them, changing the theme mode between light and dark, opening files or URLs from the Start Menu, and getting or setting clipboard contents.

How to install

Prerequisites: you need a runtime capable of running MCP stdio servers. The Windows MCP server examples use the standard MCP runtime you have installed in your environment.

Option 1: integrate via the MCP configuration in your central config file. Add the Windows server entry to your MCP config as shown:

{
  "mcpServers": {
    "windows": {
      "command": "uvx",
      "args": [
        "mcp-windows"
      ]
    }
  }
}

Option 2: run the Windows MCP server locally if you prefer a local runtime. Add this local startup entry to your MCP config:

{
  "mcpServers": {
    "windows": {
      "command": "uv",
      "args": [
        "--directory",
        "C:\\Users\\{name}\\Documents\\mcp-windows",
        "run",
        "mcp-windows"
      ]
    }
  }
}

Additional configuration and notes

Both startup options define a stdio server named windows. The first uses uvx to launch the mcp-windows tool, while the second runs uv with the directory pointing to your local copy and executes the mcp-windows routine. Ensure the path contains the actual user name and that the mcp-windows binary or script is accessible at that location.

Other important details

This MCP server exposes a suite of capabilities across media, notifications, window management, screenshot capture, monitor control, theme changes, Start Menu interactions, and clipboard access. Plan permissions and security appropriately, especially for actions that affect the Windows UI and display content.

Available tools

get_media_sessions

Retrieve active media sessions on the Windows system.

pause

Pause the currently playing media.

play

Resume or start playback for the current media session.

next

Skip to the next media track.

previous

Return to the previous media track.

send_toast

Display a toast notification on screen.

get_foreground_window_info

Fetch information about the currently focused window.

get_window_list

List all open windows.

focus_window

Bring a specified window to the foreground.

close_window

Close a targeted window.

minimize_window

Minimize a specified window.

screenshot_window

Capture a screenshot of a window.

sleep_monitors

Put connected monitors to sleep.

wake_monitors

Wake all monitors.

set_theme_mode

Switch between light and dark theme modes.

get_theme_mode

Query the current theme mode.

open_file

Open a file via the Start Menu context.

open_url

Open a URL in the default browser.

get_clipboard

Read the current clipboard contents.

set_clipboard

Write data to the clipboard.