Docs / Introduction

The Windows orchestration layer for AI agents.

WinScript bridges large language models and the Windows operating system through the Model Context Protocol, with one runtime that can speak to visible UI, application object models, and system commands.

Windows 10/11Python 3.10+MCP-ready

Native execution

Desktop control without the usual Windows fragmentation.

WinScript gives agents one automation interface instead of forcing separate tools for visible controls, Office objects, or machine commands. That makes desktop workflows easier to compose and much easier to recover when the environment shifts underneath you.

Real-time response

Direct control over native Windows surfaces without heavy wrappers between the model and the machine.

Recovery-aware

Failures return enough context for agents to retry with intent instead of guessing blindly.

Installation

WinScript is distributed through PyPI. Install it on a Windows machine with Python 3.10 or newer and connect it to the MCP client or tool host you already use.

Terminalpip
pip install winscript-mcp

Requirements

Windows 10/11 (x64)

Python 3.10 or higher

Capabilities

Claude Desktop integration

Custom MCP toolsets

Windows-first desktop automation

Getting started

A minimal setup can initialize the WinScript engine, register a tool, and expose that tool through an MCP server for your agent runtime.

agent_config.pyPython
from winscript import WinEngine, ToolRegistry

engine = WinEngine()

@ToolRegistry.register(name="open_application")
def launch_app(app_name: str):
    """Launch a native Windows application by name."""
    engine.shell.run(app_name)
    return f"Successfully launched {app_name}"

engine.serve_mcp()

Pro tip: agent autonomy

Combine WinScript with the MCP SDK so your agent can inspect system logs, restart services, or troubleshoot the environment before asking a human to intervene.