Smooth Operator Tools Server API Documentation

Overview

Welcome to the Smooth Operator Tools Server API documentation. The Smooth Operator Agent Tools are a state-of-the-art toolkit for programmers developing Computer Use Agents on Windows systems. Our powerful API handles the complex tasks of interacting with the Windows Automation Tree and Playwright browser control, while providing advanced AI functions such as identifying UI elements through screenshots and textual descriptions.

By eliminating the need to manually handle these technical challenges, developers can save significant time and effort, reaching their goals more efficiently. The Tools Server runs locally and provides comprehensive HTTP endpoints that enable LLM-based agent systems to fully control a Windows computer with precision and reliability.

Web Server

The Smooth Operator Tools Server is accessible via HTTP endpoints (GET and POST) at http://localhost:54321. This web server architecture allows for flexible computer control options:

Local Control: By default, you can control your local computer by making requests to the localhost endpoint.

Remote Control: You can also control a remote computer by opening the endpoint through your firewall and accessing it remotely. This enables powerful remote automation scenarios while maintaining security through the API key authentication.

MCP Integration

The Smooth Operator Tools Server supports Model Context Protocol (MCP), allowing AI Agents and MCP clients to automatically understand and use these endpoints. Documentation is available directly through the Tools Server API via dedicated documentation endpoints, allowing both human programmers and Language Models to understand how to use these tools.

You can make these endpoints accessible to a typical MCP client with the following configuration:

{
  "mcpServers": {
    "SmoothOperatorAgentTools": {
      "command": "smooth-operator-server.exe",
      "args": [
        "/silent",
        "/close-with-parent-process"
      ]
    }
  }
}

Note that specifying the executable without a path is sufficient because the path to the executable is included in the Path environment variable.

The /silent parameter causes the Tools Server to start without displaying any UI.

The /close-with-parent-process parameter causes the Tools Server to automatically close when the parent process (the application that started it) exits. This ensures that the Tools Server is not left running in the background when the MCP client is closed.

Authentication

Authorization: Bearer YOUR_API_KEY