mcpbeat Sign in

Arc Control (macOS) MCP Server

local only

Arc Control (macOS) runs on your own machine — the client starts it, so there is no endpoint to ping. 52 installs a week from npm. Last commit 5 Oct 2026.

Arc browser MCP for macOS: agent window, snapshots, DevTools input, guardrails

Installs per day peak 8 · avg 3 · -4% w/w
a month agotoday
52
Installs / week
npm · arc-control-mcp
2
Stars
0 open issues
5 Oct 2026
Last commit
3 releases in 90 days
MIT
License
JavaScript

What the code does

We read the source, 5 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const child = execFile(

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add arc-control-mcp -- npx -y arc-control-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.arc-control-mcp]
command = "npx"
args = ["-y", "arc-control-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "arc-control-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: ARC_MCP_LABEL (Names this agent's tab ownership. Two agents with different labels never see each other's owned tabs. Defaults to "default"), ARC_MCP_SPACE (With ARC_MCP_WINDOW=space, the Arc space new tabs open into, when a space with that name exists. Arc will not let a script create a space, so make it by hand. Defaults to "Agent"), ARC_MCP_STATE_DIR (Directory where per-session tab ownership is recorded, so a restarted agent can clean up the tabs its previous run left behind. Defaults to ~/Library/Application Support/arc-control-mcp), ARC_MCP_WINDOW ("dedicated" keeps agent tabs in one separate agent window, never the user's own. "space" puts them in the Agent space of the user's window. Defaults to "dedicated"), ARC_MCP_WINDOW_PLACEMENT (Where the agent window goes once, at creation: "auto" (largest non-main display, else where Arc puts it), "second-display", "minimized" (experimental) or "none". Needs Accessibility. Defaults to "auto"), ARC_MCP_IDLE_MS (How many milliseconds the user must have been idle before the server does anything visible. 0 turns the activity gate off. Defaults to 1500), ARC_MCP_IDLE_WAIT_MS (How many milliseconds to wait for that pause before failing with userActive true. Defaults to 15000), ARC_MCP_ARC_DATA_DIR (Directory the local data tools (sidebar_tree, find_stale_tabs, search_archive, search_history) read Arc's files from. Defaults to ~/Library/Application Support/Arc), ARC_MCP_ALLOW_HISTORY (Set to 1 to let search_history run. Off by default, and any other value leaves it off), ARC_MCP_CDP (Set to 0 to disable the DevTools engine (trusted input, screenshots, console and network capture). On by default, and inert until Arc is launched with --remote-debugging-port), ARC_MCP_CDP_PORT (The DevTools port to probe on 127.0.0.1. The host is fixed. Defaults to 9222), ARC_MCP_ALLOWED_ORIGINS (Guardrail. Comma list of origins the agent may touch (host, *.host, scheme://host[:port], file://, about:). Anything not listed is refused. Unset means no allow list), ARC_MCP_BLOCKED_ORIGINS (Guardrail. Comma list of origins the agent may not touch. Wins over the allow list. Unset means no block list), ARC_MCP_BLOCK_READS (Set to 1 to apply the origin lists to read tools as well as changing ones. Off by default), ARC_MCP_READ_ONLY (Set to 1 to expose only the read-only tools. Off by default), ARC_MCP_AUDIT_LOG (Path of a file that gets one JSON line per changing call (time, tool, tab, origin, ok, error), never typed values or script code. Unset means no audit log).

Alternatives to Arc Control (macOS)

same job, measured the same way
openDAW MCP
by ameobius

262 MCP tools for agent-native control of openDAW, a browser-based DAW

local only
Toolpiper
by modelpiper

On-device MCP tools for macOS: local AI, speech, vision, browser automation, system control.

local only
Selenium MCP
by gaforov

Selenium MCP server for AI agents — 41 browser automation tools with snapshots and sessions.

82 installs/wk local only
Safari DevTools MCP
by hayodev

MCP server for Safari DevTools — browser debugging and automation for AI coding agents

119 installs/wk local only
PilotGentic
by pilotgentic

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

264 installs/wk local only
Ghost
by northtekdevs

Verified desktop control for agents on Windows and Linux: apps with no API, windows, shell, browser.

local only
Desktop MCP
by jaimenbell

Windows desktop-control MCP server: screenshot, window mgmt, mouse/keyboard input, recording.

111 installs/wk local only
CloakMCP
by overtimepog

Stealth browser MCP server — anti-detection Chromium with snapshot-first agent interface

135 installs/wk local only

Arc Control (macOS) — questions

Answers built from our own checks of this server.

Why is there no uptime for Arc Control (macOS)?
Arc Control (macOS) runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package arc-control-mcp was installed 52 times last week.
How do I connect Arc Control (macOS)?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls arc-control-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Arc Control (macOS)?
The npm package arc-control-mcp was installed 52 times in the last week. Week over week that is -4%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Arc Control (macOS) open source?
Yes — it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.