Omniparser Autogui MCP Server

If you want an AI assistant working directly with Omniparser Autogui MCP, the omniparser autogui mcp mcp server is the bridge. This is an MCP server that analyzes the screen with OmniParser and automatically operates the GUI. Confirmed on Windows.

What Omniparser Autogui MCP does

This is an MCP server that analyzes the screen with OmniParser and automatically operates the GUI. Confirmed on Windows.

Installing the omniparser autogui mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

The server reads 5 environment variables: PYTHONIOENCODING, OCR_LANG, CLONED_PATH, SOM_MODEL_PATH, CAPTION_MODEL_PATH. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Omniparser Autogui MCP sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by NON906.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the omniparser autogui mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.