Log inSubmit server
Native DevTools logo

Native DevTools

Automates macOS, Windows, Chrome/Electron, and Android interfaces locally through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Native DevTools

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "native-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "native-devtools-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y native-devtools-mcp

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 6d ago.

Overview

Native DevTools MCP server connects AI clients to native desktop apps, Chrome/Electron targets, and Android devices for local UI automation. It combines screenshots, OCR, accessibility and DOM inspection, simulated input, Chrome DevTools Protocol, and Android Debug Bridge workflows. Reach for it when one MCP endpoint must automate headed applications across macOS, Windows, Chrome/Electron, and Android rather than only web pages.

Use cases

  • Automate native macOS and Windows application workflows
  • Test Chrome and Electron interfaces through CDP
  • Control Android devices over USB or Wi-Fi with ADB
  • Inspect screens and locate controls with OCR or accessibility data

Key features

  • Desktop screenshots, OCR, and input simulation
  • macOS accessibility-tree interaction
  • Chrome and Electron CDP automation
  • Android ADB and uiautomator controls
  • Window management and image matching
  • Local execution without remote data transfer

Tools13

What Native DevTools lets your agent do. Expand a tool for its parameters.

Self-reported~171 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

10/10 checks healthy over the last 49d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · native-devtools-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars139Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed13Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Native DevTools works

What Native DevTools does

Native DevTools MCP server gives MCP clients local control over supported desktop, browser, Electron, and Android interfaces. It can capture screens, recognize text, locate accessibility or DOM elements, send clicks and keyboard input, manage windows, and interact with Android devices through ADB.

The server supports three main interaction paths. Visual automation uses screenshots, OCR, coordinate-based input, and image matching for applications that do not expose a useful accessibility tree. macOS accessibility dispatch targets native AppKit and SwiftUI elements directly. Chrome DevTools Protocol handles Chrome and Electron applications when remote debugging is enabled. Android operations use ADB and uiautomator for device discovery, screen capture, text lookup, input, and app management.

How it works

The server runs locally and communicates with an MCP client over the client’s configured command. Screenshots and input remain on the machine. A typical workflow starts by selecting the interaction method for the target: visual tools for broad compatibility, accessibility dispatch for native macOS controls, CDP for web or Electron content, or ADB for Android.

For Android, android_list_devices discovers connected devices, while android_connect selects one by serial number. The Android tool set can then capture screens, find text, tap coordinates, swipe, type, press keys, launch packages, list installed apps, and inspect display or foreground-activity details.

Setup and configuration

Run the Native DevTools MCP server without a global install using:

Terminal
npx -y native-devtools-mcp

It requires Node.js 18 or later. A global npm installation is also supported, and the repository provides Rust build instructions for users who want to build from source. MCP clients can use the npx command with -y native-devtools-mcp as the server configuration.

Android automation additionally requires an ADB-connected device over USB or Wi-Fi.

Tools and capabilities

The Native DevTools MCP server supports:

  • Screen, window, or region screenshots with OCR on macOS and Windows.
  • Mouse and keyboard simulation, including clicks, drags, scrolling, and text entry.
  • macOS accessibility snapshots and element actions such as click, set value, and select.
  • Chrome/Electron DOM actions, navigation, snapshots, filling, clicking, and JavaScript evaluation through CDP.
  • Image-template matching for controls that OCR or accessibility data cannot identify.
  • Window listing, focus, application launch and quit, and timestamped window recording.
  • Android screenshots, text lookup, gestures, key presses, package operations, and device information.

Limitations and notes

The Native DevTools MCP server supports macOS, Windows, Chrome, Electron, and Android, but not Linux or iOS. Browser automation is limited to Chrome and Electron through CDP; Firefox and WebKit are not supported. It is headed automation that depends on permissions and a real machine, not a headless CI test grid.

macOS accessibility dispatch is intended for native macOS applications and does not replace visual or CDP workflows for every target. CDP also requires Chrome or Electron to expose a remote debugging port. Android capabilities depend on ADB connectivity and the selected device. The server is local, so the applications and devices being controlled must be available to the host running it.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Native DevTools

Native DevTools is an MCP server that connects AI clients to macOS and Windows desktop apps, Chrome and Electron through CDP, and Android devices through ADB. Its main tools provide screenshots, OCR, accessibility or DOM lookup, simulated input, window control, Android device operations, and app management, running locally on the host machine.

Run `npx -y native-devtools-mcp` and configure that command in your MCP client. You can also install it globally with npm or build it from the Rust source. Node.js 18 or newer is required for the npx-based setup.

Yes, Native DevTools works with Cursor through an MCP configuration using `npx -y native-devtools-mcp`. The README also provides a Cursor installation link and lists Claude Desktop, Claude Code, and other MCP-compatible clients.

Native DevTools needs Accessibility and Screen Recording permissions on macOS. These permissions allow the server to inspect and control native applications and capture their screens.

No. Browser automation supports Chrome and Electron through CDP, not Firefox or WebKit, and the server does not support iOS. Android is supported through ADB.

Related MCP servers

All in OS Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNative DevTools AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/native-devtools?style=directory)](https://allmcps.com/mcp/native-devtools)
HTML Embed
<a href="https://allmcps.com/mcp/native-devtools"><img src="https://allmcps.com/api/badge/native-devtools?style=directory" alt="Native DevTools on AllMCPs" /></a>