PilotGentic

com.pilotgenticPublished by pilotgentic.comv1.0.0Updated Oct 24, 2026

macOS desktop control for Claude: click, type, screenshot, AX tree, browser control, agentic loops.

The publisher's own server: QuickBooks Connector by Meridian

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

A macOS desktop-control MCP server that lets an assistant click, type, take screenshots, read the accessibility tree and drive a browser.

What you can do
Control the macOS desktop by clicking and typing into applications and windows, as described in the registry entry. Capture screenshots to see what is on screen. Read the accessibility (AX) tree to inspect interface elements. Drive a browser as part of the same desktop control. Run agentic loops that repeat these actions toward a goal.
When to use it
Useful when an assistant needs to operate macOS applications directly, such as filling in forms, navigating a browser, or checking what is displayed on screen, rather than working only through files or APIs.
Requirements
Runs as a local process on the user's machine, installed from the npm package @pilotgentic/mcp-server over stdio. It is macOS desktop only. No authentication, environment variables or headers are declared.
Before you install
It can click and type in real applications, so actions may change data, submit forms or trigger purchases without confirmation. Screenshots and the accessibility tree expose whatever is on screen, including sensitive content. Granting macOS accessibility and screen-recording permissions gives the server broad control of the desktop.

Installation

In SourceWeft

  1. Open PilotGentic in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Pilot integrations