Omni MCP Server

A 1:1 replica of Claude Desktop's computer-use tool surface, for Windows and the Claude Code CLI.

Local serverstdioPython

What is the Omni MCP server?

Omni MCP server exists for a simple reason — assistants are far more useful when they can act on Omni directly instead of describing what you should do. A 1:1 replica of Claude Desktop's computer-use tool surface, for Windows and the Claude Code CLI.

What you get

A faithful 1:1 replica of Anthropic's official computer-use tool surface — shipped as a plain MCP server for Windows. It lets the Claude Code CLI (or any MCP client) drive the Windows desktop the way Claude Desktop's built-in computer-use does: screenshots, mouse / keyboard / scroll / drag / batch input, clipboard, multi-monitor, and application launch.

Setting it up

Installation goes through your MCP client rather than a global install: point it at fetch on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Omni is connected, these are the calls the assistant has available:

  • deactivate — end the session without killing the process (glow off, controlling window restored, grants revoked); the counterpart to request_access
  • display_overview — one composite, labeled image of all monitors laid out per the virtual-desktop arrangement (an orientation aid for "which screen is that window on?"

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the omni mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Omni's toolset — deactivate, display_overview — is a fair guide to whether it matches your workflow. It is maintained by Jason26214; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
deactivateend the session without killing the process (glow off, controlling window restored, grants revoked); the counterpart to request_access.
display_overviewone composite, labeled image of all monitors laid out per the virtual-desktop arrangement (an orientation aid for "which screen is that window on?"; not a click surface).

How to install the Omni MCP server

{
  "mcpServers": {
    "omni-computer-use": {
      "command": "uvx",
      "args": ["fetch"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Omni to deactivate.
  • Use Omni to display overview.

Frequently asked questions

It connects Omni to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (deactivate, display_overview) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Omni directly.